Public onboarding · governed execution
Request your own Veloce OS.
Anyone can start here. Veloce turns an approved scope into one isolated client operating system with visible capabilities, a personal provider page, transparent credits, approval checkpoints, and tenant-scoped data.
Provisioning path
- 1You submit requirements, operating scope, tools, budget, and approval rules.
- 2Veloce returns a scope recommendation and quote for operator approval before payment.
- 3You verify your email; approved payment and manifest review happen before activation.
- 4The control plane compiles the approved scope into a tenant manifest, provisions an isolated runtime, and runs its evidence bundle.
- 5You enter the portal and connect BYOK or Veloce-managed providers server-side.
Runtime guardrails
- No raw 3939 operator workspace exposure
- Cloud Run service gated to approved identities
- Client-owned credentials or written managed allowance
- Secret Manager for provider keys and OAuth material
- Human approval before external actions
- Budget caps and warning thresholds
- Tenant-scoped memory, files, and audit logs
Public signup
Describe the operation you want to build.
Veloce uses your answers to recommend a scope and quote. Never paste credentials into intake. After approval and payment, add BYOK keys or choose managed credits in your private portal.