Free & self-hosted Your code and keys never leave your infrastructure
Describe a product in a sentence. Review the plan before a byte is written. Get a repository that compiles, migrates and runs — with row-level security, audit, tests and human gates already in it. Self-hosted, free, and yours.
No signup to look. Nothing to install until you want a repository.
Rathvan = intake & scoping + architecture review + scaffolding + security foundations + gates + provenance + deploy verification
Every number on this page is generated from the sources at build time. If one is wrong, the build fails — which is the same rule the platform applies to everything it produces.
Solutions
The pipeline is 13 stages and 3 human gates. A track tightens the stages that matter for the work and relaxes the ones that do not. What it never does is let a prototype reach production by accident.
Structurally incapable of shipping: separate namespace, no production credentials, an expiry. Promotion is a restart, not a merge.
Identity, tenancy, forced row-level security, audit and tests in the first commit — the parts every product needs and nobody enjoys building twice.
Server-priced from the catalogue, integers in the smallest unit, and the full security pass. The rules are gates, not guidance.
Drift detection reads your docs against the facts, drafts the smallest correct edit, and opens a pull request. It never merges one.
Demo
Three products scaffolded by the real tool, captured and published: the config that went in, the plan it printed before writing a byte — including what it refused — and the files that came out, provenance included.
Compare
Not a vendor scoreboard. These are the real alternatives: hand the work to a coding agent, or build the foundations yourself again.
| Coding agent alone | Building it yourself | Rathvan | |
|---|---|---|---|
| Plan before code | Sometimes, in prose | In your head | Printed, and nothing is written until you accept it |
| Security foundations | Whatever it remembered | Week three, usually | RLS enabled and forced, in the first commit |
| Human gates | None that block | Process, if people follow it | Executable — the build stops |
| Where it can ship | Anywhere it is pointed | Anywhere | Staging is the ceiling; production needs a person |
| Provenance | A chat log | Git history, if you look | Every file hashed, the builder and kernel recorded |
| Your code, your keys | Their servers | Yours | Self-hosted; bring your own model keys |
Rathvan is not a replacement for a coding agent — it is what decides whether the agent's output is allowed to become your product.
Download
Answer the intake in the console, download your rathvan.json, and turn it into a repository:
$ npx "https://build.rathvan.com/rathvan-cli.tgz?v=fe97e7eabfb1" new ./your-product
The plan prints first and writes nothing until you confirm. Java 21 and Docker are the only prerequisites.
One command, no install, no account. Every scaffold carries a lock file recording which builder and kernel produced it.
A macOS image with a bundled Java runtime — nothing else to install. Your machine, your keys, your data, its own console.
Enterprise
Self-hosted from the first day, so your code and credentials never leave your infrastructure. SSO, per-user credentials with revocation, spend budgets, audit, and a model chain that fails over across vendors rather than failing. Repository access is granted per repository and revocable by you.