This release is a pre-release and may not be stable for production use.
Gliss
An experimental codec for streaming VM desktops to the browser. A Rust server captures a VM over VNC, encodes on the CPU and forwards keyboard and mouse input back. The browser needs no GPU, guest agent or plugin. Alpha quality. The code, experiments and docs were written entirely by AI agents. Laurent Gonzalez provided the infrastructure and oversaw the work.
| Workload (1280×800 VM, CPU only) | Stack | p95 response | Traffic |
|---|---|---|---|
| Terminal typing, 40 ms RTT | Gliss Batch (lossless) | 212 ms | 0.19 Mbit/s |
| Gliss H.264 | 213 ms | 0.10 Mbit/s | |
| Guacamole | 218 ms | 0.05 Mbit/s | |
| Moving desktop, 150 ms RTT + 1% loss | Gliss all-IDR H.264 | 460–464 ms | 4.2 Mbit/s |
| WebRTC H.264 (aiortc) | failed: missed inputs | 0.85 Mbit/s | |
| WebRTC VP8 (aiortc) | failed: missed inputs | 0.5 Mbit/s |
1 maintainer
Metadata
1 maintainer
Release files for gliss-server 0.1.0a2
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 | Reset |
|---|---|---|---|---|
| gliss_server-0.1.0a2-py3-none-manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64 | Details |
| gliss_server-0.1.0a2-py3-none-manylinux_2_28_aarch64.whl | Python 3 | none | Linux glibc 2.28+ ARM64 | Details |
Total release size: 8.7 MB
Release files / gliss_server-0.1.0a2-py3-none-manylinux_2_28_x86_64.whl
| Download URL | gliss_server-0.1.0a2-py3-none-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
084f53946f91f4d53b05b289ecff33190d48c0243d74ce1182c225f7056bd9d2
|
|
BLAKE2b-256 checksum How to use checksums |
d162b094a8fc972dd39c6f11a5b9dc75da275c564e16a66d7b3dde68a93cb482
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 26, 2026.
Transparency logRelease files / gliss_server-0.1.0a2-py3-none-manylinux_2_28_aarch64.whl
| Download URL | gliss_server-0.1.0a2-py3-none-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
9520548a69f0c1b05545b59cc58798f0e3aaa1c16e203591df4198ac597a027d
|
|
BLAKE2b-256 checksum How to use checksums |
095603cc47d3322a29c2f881607358af3a333744b09b5749477cfa1ba8564def
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 26, 2026.
Transparency logSecurity for gliss-server 0.1.0a2
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for gliss_server-0.1.0a2-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 26, 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.
