VoltroDocumentation

Why Voltro?

The wager Voltro is making — reactive, multi-tenant, AI-first as primitives instead of libraries you bolt on.

Most frameworks make you re-derive the same primitives every time: auth, tenants, audit logs, billing, real-time updates, background jobs. Voltro ships them as first-class composable primitives so you can spend your time on what makes YOUR product different.

The wager

AI agents will increasingly write your code. The frameworks that win are the ones that give agents a stable, opinionated surface to target — not a thousand decisions every project re-litigates.

Voltro is deliberately opinionated about boring things (HTTP, state, transport, schema) so the only decisions left are the ones that matter for your product.

Where Voltro fits

You're building... Voltro is a good fit when...
A multi-tenant SaaS You want tenant isolation enforced by the runtime, not "by hope" in app code
A real-time collaboration app Live data should be the default, not a feature flag
An AI agent product Tool calling, RAG, streaming, durability should be primitives
A control plane You need durable workflows + audit logs + RBAC out of the box

Where Voltro is a bad fit

  • You need an existing JS/TS ecosystem feature on day one. Voltro is pre-release; APIs change.
  • You're publishing to a CDN-only edge. Voltro is a stateful, long-running runtime — Vercel, Fly, Railway, Render, or self-host on a Node 24 box.
  • You want a visual ORM / GUI builder. The CLI + your editor + LLMs are the editor.

What we won't do

  • Lock you in. Self-hosting is fully supported. Cloud is the premium tier of the same open-core runtime, not a fork.
  • Multi-runtime grab-bag. Effect-TS end-to-end — no Restate, no Temporal, no Inngest, not even opt-in.
  • Magic. Every file convention is documented; every generated file lives in .framework/ and you can read it.
  • Codegen you have to remember to run. Schema flows from your tables to your React components automatically via Vite's module graph.