This release is a pre-release and may not be stable for production use.
Ritvo
Ritvo is an open-source authority layer for AI agents. When an agent asks to do something its bindings do not clearly allow, Ritvo decides who may approve it, escalates along named roles, enforces separation of duties, and keeps the evidence in a tamper-evident ledger.
The name comes from the Sanskrit ṛta, the right order of things.
Status
Early, pre-alpha. The ritvo package on PyPI (version 0.0.1.dev0) is a placeholder that reserves the name. It contains only the ritvo --version command and no features. Nothing here is ready for production use. Interfaces, file formats and commands will change without notice until the first feature release, v0.1. See CHANGELOG.md for what exists today.
Where Ritvo sits
Gateways sit between an agent and its tools. Ritvo sits below them, next to the resource, and above them as the policy authority:
- Enforcement points run next to the resource. The first is middleware inside your own MCP server, added with one library call and removed the same way. They work behind any gateway, or none.
- The Governance OS publishes signed policy bundles to enforcement points, resolves asks along escalation ladders, and mints single-use grants. It never touches a live call.
- The inspector (
ritvo inspect) is a local, read-only scan of the MCP servers and agent frameworks you name. It writes an inventory and a report; it sends nothing anywhere. - The diagnostic (
ritvo review,ritvo diagnose) reads files and writes a gap report and a draftritvo.yaml. It never connects to anything.
The design is in docs/PRD.md (what and why) and docs/SPEC.md (behaviour and interfaces). Why Ritvo is not a gateway is recorded in docs/decisions/0001-below-the-gateway.md.
Non-goals
- Not a gateway. No key issuance, budgets, provider proxying or tool allow lists. Those are well served elsewhere.
- No credential custody, no TLS interception, no autonomy scoring, no agent-authored intent.
- Not multi-tenant SaaS. One instance per organisation, plus the library inside that organisation's own MCP server.
- No vertical policy content.
- Not a security scanner for prompt injection or malicious tool descriptions.
Quick start
There is nothing to run yet beyond the CLI entry point. To install from source:
git clone https://github.com/Ritvo-ai/ritvo.git
cd ritvo
python3.12 -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -e .
ritvo --version
The quick start will cover ritvo inspect and ritvo review as they land, and ritvo demo on examples/mcp-demo after that.
Getting help
See SUPPORT.md. Report security issues privately as described in SECURITY.md, never in a public issue.
Contributing
See CONTRIBUTING.md. Every commit needs a DCO sign-off. Please read the Code of Conduct.
Licence
Apache-2.0. See LICENSE and NOTICE. The name Ritvo is covered by TRADEMARK.md.
Metadata
Release files for ritvo 0.0.1.dev0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ritvo-0.0.1.dev0.tar.gz | 39.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ritvo-0.0.1.dev0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.7 kB
Release files / ritvo-0.0.1.dev0.tar.gz
| Download URL | ritvo-0.0.1.dev0.tar.gz |
|---|---|
| Size | 39.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
244cef76a99c2882182fe1e16051f019af2345fbca9a4c0f343fefe3917d3352
|
|
BLAKE2b-256 checksum How to use checksums |
cde779bdd7700e213e1298634fb6e9c4b0b0e6f209a3ffec087c950645c481da
|
| 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 14, 2026.
Transparency logRelease files / ritvo-0.0.1.dev0-py3-none-any.whl
| Download URL | ritvo-0.0.1.dev0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71e4705ac9e14fd1cec758195d65a452d6c4890c4b943587d564774db92c7643
|
|
BLAKE2b-256 checksum How to use checksums |
31a49ac2951434bf0331b03186bd403146b187b86a74ddb8f9b92b6009e05711
|
| 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 14, 2026.
Transparency log