What is supported
- CPython 3.13 from Debian 13, installed on the nodes by the platform and kept up to date with security updates. An application is placed only on a node whose python3 has the same minor version.
- FastAPI and uvicorn, compiled wheels such as pydantic-core included. The entry point is [tool.gluonify] entry in pyproject.toml (run as python3 -m), or the single entry of [project.scripts].
- The SDK gluonify[fastapi]: Charm tokens (incoming tokens checked, application tokens to services), configuration and secrets from Top, and gDown through the neo4j driver over Bolt+TLS (bolt+s://, internal authority provided; plain bolt:// is refused).
- "uses" inferred at build time: Bup reads the installed distributions without importing anything (gluonify gives charm, neo4j gives gdown); gluonify.json stays optional.
- The port is given in the variable named in gluonify.json (PORT in the starter app) and the health path is yours (/health/ready, /health/live in the starter app).
pyproject.toml: the entry point
[project] name = "my-service" requires-python = "==3.13.*" dependencies = ["gluonify[fastapi]"] [tool.gluonify] entry = "my_service.main"
What Bup checks
- A lock file: requirements.lock pinned with hashes (or exported by uv export --frozen), installed with pip --require-hashes, wheels only, from the platform index only. Editable, path and URL lines are refused.
- A Sonar analysis of your code, and dangerous-call rules (eval, exec, pickle, shell=True, os.system, yaml.load without SafeLoader): a repository that breaks them is refused before anything is built.
- pip-audit on the dependencies, with the same organisation policy as Maven and npm: a vulnerability without a severity rating counts as critical.
- A signed gzip archive: a launcher, your code compiled to .pyc and the site-packages of the venv, without pip; published, stored and signed (Ed25519 provenance) exactly like a native executable.
The sandbox
A Python application runs in the same systemd sandbox as a native one: its own account, folder and network, ProtectSystem=strict, NoNewPrivileges, no capability, a seccomp filter, and MemoryDenyWriteExecute=yes. CPython without a JIT never needs memory that is both writable and executable, and ctypes callbacks work under this protection. The interpreter starts isolated (python3 -I -S -B): only your code and the venv are on sys.path.
Sleep and wake
Sleep mode works as for native applications: an idle Python application is stopped, and the next request through the ingress wakes it up; the request is held, not lost.
Measured figures
FastAPI and uvicorn on the CPython 3.13.5 of the node, measured on 2026-10-14 with a real agent and orchestrator, in a Debian 13 container with a real systemd.
- arm64 (Apple M4 Max, Docker Desktop) — Artifact (gzip) 4.9 MB, Memory (RSS) 48.6–48.7 MB, Wake on request 0.61 s
Measured on arm64 (Apple M4 Max), a minimal service, a few runs per case. Build time and build memory are not measured yet.
The starter app
gluonify-source-python is the starter app in Python: the same service as gluonify-source (REST, Charm, Top, gDown, health), with its pyproject.toml and its lock file. It passes 29 of 29 end-to-end checks on a real cluster: Charm tokens, Top, gDown over Bolt+TLS, inferred uses, sleep and wake.
Limits
- The SDK gluonify[fastapi] is not on PyPI yet. Until then it is installed from its repository, which the lock-file rule of Bup does not accept for a real build.
- Python 3.13 only: no other Python version, because the interpreter is the one of the nodes.
- No JIT for C extensions, and not the experimental JIT of CPython either: MemoryDenyWriteExecute forbids memory that is writable and executable.