Ship fast.
Still keep control.
A schema change or a spend spike shouldn’t be able to surprise you. Cloud adds a governance layer over your apps: migrations are reviewed and approved before they run, usage is metered against quotas, and entitlements travel in a signed license the app verifies offline.
# Your pipeline submits a plan for review:
$ voltro db plan --json | voltro cloud migrations submit
→ plan mig_01J8Z… submitted
# A reviewer gets a signed, session-free link (7-day exp):
https://voltro.cloud/review/mig_01J8Z…?sig=…
✓ approved by owner@team.co (immutable trail)
# apply stays in YOUR pipeline — Cloud never runs it:
$ voltro db applyWhat governance covers
Everything on this page is shipped today.
Migration approvals
ShippedYour pipeline submits a `voltro db plan`; a reviewer approves it before it runs. The decision is an immutable, role-gated record — the org owner or an admin signs off, and the trail is permanent.
Signed review links
ShippedA reviewer can act without a dashboard session: HMAC-signed review URLs carry the plan id and a 7-day expiry, verified in constant time. Send the link, get the sign-off.
The dashboard never applies schema
ShippedBy design, Cloud reviews but does not run your migrations — apply stays `voltro db apply` in your pipeline. Multi-environment tabs (dev / staging / prod) show per-env fingerprint drift.
Destructive-change wall
ShippedThe deploy pipeline classifies additive vs destructive migrations and halts destructive ones into the approval flow before any traffic moves.
Usage metering & quotas
ShippedThe platform accrues vCPU-seconds and GB-seconds per app into a monthly bucket and shows quota meters against the free-tier cap. Metering is record-only — no silent auto-suspend on approximate data.
License issuance
ShippedCloud is the signing authority: it issues EdDSA (Ed25519) license tokens carrying edition, entitlements and feature flags. Apps fetch and verify them offline, so plan decisions never bake into a published package.
Why the approval flow matters
The gap self-host leaves open
Self-hosting gives you `voltro db apply` and nothing between an engineer and production schema. On regulated or multi-person teams that’s a hole. Cloud closes it with a submit → review → approve gate and a permanent, signed trail of who approved what — without slowing additive changes, which pass straight through.
Related capabilities
See it running.
Open the dashboard on a live demo project and click through the panels yourself — logs, traces, workflows, migrations and more.