Pyro

Pyro is a Rust-native Python application runtime for backend services.

The goal is a drop-in replacement for CPython on safe-mode, pure-Python backend applications: the same application code, the same upstream wheels, CPython-like behavior on supported workloads, and a smaller, memory-safe runtime built around production Rust components.

Pyro is in active development. The source is not published here yet.

What Pyro Is

Pyro targets backend applications that can run without arbitrary third-party C extensions. It is not a rewrite of Django, FastAPI, httpx, pydantic, or other ecosystem packages in Rust. Those packages should run as their real upstream wheels on the Pyro interpreter.

The runtime owns the interpreter and CPython-compatibility adapter layers, then delegates operating-system and standard-library work to mature components:

• Tokio for async I/O and scheduling
• std::thread and std::sync for threading primitives
• libsqlite3 via Rust bindings for SQLite
• serde_json, fancy-regex, TLS, DNS, and other focused libraries for stdlib surfaces

The v1 release bar is CPython-compatible behavior for covered pure-Python backend workloads, with at least 2x speed and no more than 50% RSS on covered release benchmarks.

Scope

Pyro v1 is aimed at:

• Django ASGI applications
• FastAPI and Starlette services
• aiohttp and httpx clients
• pure-Python build and packaging toolchains
• self-contained install, lock, run, pack, doctor, and repl workflows without a system Python requirement

Pyro v1 is not aimed at arbitrary native-extension workloads such as NumPy, pandas, Pillow, or cryptography-heavy applications unless a future safe provider exists.

Status

Development is currently private on the project's working forge. This public repository is a preview page while the runtime is prepared for source publication.

When the source opens here, the repository will move directly onto the active main branch and this frontpage will remain the entry point into the project docs.

Availability

Pyro is not ready for production use yet. Public source, installation instructions, release artifacts, and contribution guidance will be published here when the v1 compatibility and evidence gates are ready for wider review.