Andris - A Rust SPICE Server for an Existing X11 Desktop
Andris is a SPICE (Simple Protocol for Independent Computing Environments) server, written in Rust, for a Linux desktop that is already running. It attaches to an existing X11 display and serves it to a SPICE client, in particular ryll, optionally through the kerbside SPICE proxy. It is aimed at people who reach a Linux machine's desktop remotely, above all the session behind xrdp, so that RDP and SPICE can show the same desktop at once.
Andris connects to the display as an ordinary X client and never starts a desktop of its own. It works with an X server that has a 32-bit BGRX root window and the XTEST, XFIXES, XKEYBOARD and DAMAGE extensions -- Xorg, the xorgxrdp session behind xrdp, or Xvfb, for instance -- and checks for them before it listens. That sets it apart from its neighbours: Xspice is an Xorg driver that starts a new display, and QEMU's SPICE server shows a virtual machine's screen. Its closest relative is x11spice.
Andris does not support Wayland. It needs a real X11 desktop: an XWayland display holds only the X applications of a Wayland session, not the desktop itself.
Andris is a sibling of ryll: it builds on ryll's shared
shakenfist-spice-* protocol and compression crates, and sends only
message types that kerbside's allowlist accepts.
Status
Andris is pre-alpha. It exports an X display to one client at a time, with the main, display, inputs, cursor and playback channels: you get the desktop, a keyboard, a mouse, a pointer shape, text clipboard and resizing where the X server allows it, video areas as H.264 streams to clients that support it, and the desktop's sound. Install it from PyPI and run it against a display:
pipx install andris
(umask 077; head -c 24 /dev/urandom | base64 > ticket)
DISPLAY=:10 andris --ticket-file ticket
To run it as a service beside xrdp, andris install-unit sets up its
systemd unit; see
Running andris alongside xrdp.
To build it from source, see
Running andris.
What andris is meant to become, and the order in which it is being built, is set out in the X11 desktop over SPICE master plan.
Documentation
- Documentation index - Where andris's documentation lives
- Plans index - Every planning document and its status
- X11 desktop over SPICE - The master plan: what andris is for and how it will be built
- Running andris - Options, the ticket file, TLS, connecting with ryll and fronting andris with kerbside
- Running andris alongside xrdp - The systemd user unit, and how RDP and SPICE share a desktop
- Development - Building, testing and the CI pipeline
- Releasing andris - Publishing the wheels to PyPI
Project reference files:
- ARCHITECTURE.md - Andris's components, data flow and relationship to ryll and kerbside
- AGENTS.md - Guide for AI coding assistants
License
Apache-2.0
Metadata
Release files for andris 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| andris-0.1.0-py3-none-manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64 | Details for andris-0.1.0-py3-none-manylinux_2_28_x86_64.whl |
| andris-0.1.0-py3-none-manylinux_2_28_aarch64.whl | Python 3 | none | Linux glibc 2.28+ ARM64 | Details for andris-0.1.0-py3-none-manylinux_2_28_aarch64.whl |
Total release size: 8.5 MB
Release files / andris-0.1.0-py3-none-manylinux_2_28_x86_64.whl
| Download URL | andris-0.1.0-py3-none-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
802b51b7279d155f0825dea8950eb5e8838db1c58afb67ce6513caa83fc2a355
|
|
BLAKE2b-256 checksum How to use checksums |
4e792ea74081210377b5f4f3349092c5ae6179d94d3b2f8c6ea7331cca84d531
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logRelease files / andris-0.1.0-py3-none-manylinux_2_28_aarch64.whl
| Download URL | andris-0.1.0-py3-none-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 4.2 MB |
| Tags | Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
9a7a3945bf10ec4b223db4583a0e9d276d5448e2b8a9824a6fde67f434ea2f7e
|
|
BLAKE2b-256 checksum How to use checksums |
3e8d3b3bab8746eb1e474c7ce3e90c0ab36089b81cf63efcb86192c388e276d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logSecurity for andris 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for andris-0.1.0-py3-none-manylinux_2_28_x86_64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.