One command line,
create-project to production.
The voltro CLI is the whole workflow: scaffold a project, run the dev loop with automatic codegen, plan and apply migrations, build and deploy, inspect a running app, and check the blast radius of a change. It reports zero telemetry.
$ voltro create-project my-app
$ voltro dev # codegen on every change
$ voltro db plan # diff schema → migration
$ voltro db apply
$ voltro check --diff # blast radius of a change
$ voltro build && voltro startThe command surface, by job.
Scaffold anything
voltro create-project (with --api / --web / --cache=redis / --baseline), add-app, package create for publishable or private packages, and generate "[prompt]" for the AI app-builder (dry-run unless --write).
A dev loop with no codegen step
voltro dev writes rpcGroup.generated.ts and the typed client on every change via the module graph — there is no separate codegen command to forget. Generated files live in .framework/ and are disposable.
Database, planned
voltro db plan / apply / drift / squash / rollback / restore-snapshot / status / seed, plus embeddings backfill — file-based, online-safe migrations with drift detection across environments.
Build, run & deploy
voltro build / start / serve, baseline (bare / compose / helm), static (Cloudflare Pages / S3 / Netlify), serverless (Cloudflare / Scaleway) and dormancy for scale-to-zero.
Inspect & check
voltro inspect / logs / traces / workflows / cluster read a running app; voltro check validates against its live manifest — dangling source/target tables, unknown RBAC scopes, orphan tables — with --json and --diff.
Data, secrets & cloud
voltro data export / import / backup / restore (portable .vbundle with masking + encryption), secret generate for every purpose, and voltro cloud (login / whoami / projects / env / import).
check knows what your change will break.
Blast-radius checks against the live app
voltro check doesn’t lint files — it validates against the running app’s live capability manifest, catching dangling source/target tables, unknown RBAC scopes and broken route bindings before they ship. --diff previews the blast radius of a removal, and --json emits LLM-shaped diagnostics so an agent can fix its own mistakes in a loop.
The CLI drives the whole runtime.
Open the framework. See it for yourself.
Every primitive on this page is in the framework today. Clone the starter, run `voltro dev`, and have it on screen in two minutes.