Pricing
Controlled agent work,
Controlled agent work,
priced for pilots.
Start with the shipped flow: create an agent, give it credits, connect GitHub, set spend and approval rules, run tasks, and inspect every action.
Builder access
For trying one controlled agent against the GitHub issue flow.
$0/ forever
- ✓ 1 controlled agent
- ✓ Promotional credits
- ✓ Task, run, output, debit, audit, rerun
- ✓ GitHub issue creation tool
- ✓ Basic spend and permission rules
- ✓ Early access support
Team pilot
For teams validating controlled GitHub issue work before a broader rollout.
Pilot access
- ✓ Multiple controlled agents by request
- ✓ GitHub App install and repo linking
- ✓ Approval queue and stored-payload resume
- ✓ Monthly and per-action spend controls
- ✓ Run steps and audit history
- ✓ Denied-action and GitHub failure alerts
- ✓ Email support during pilot
Production prep
For organizations preparing a controlled rollout of the current product.
Custom
- ✓ Scoped rollout planning
- ✓ Supabase migration and RLS review
- ✓ GitHub App setup guidance
- ✓ Environment and alerting checklist
- ✓ DB-backed isolation test plan
- ✓ Security review of the shipped flow
- ✓ Dedicated onboarding
All early access plans focus on the implemented controlled-agent and GitHub issue flow. Public API authorization, payment products, and developer runtimes are not included yet.
Compare every plan
| Feature | Builder access | Team pilot | Production prep |
|---|---|---|---|
| Agent workflow | |||
| Controlled agents | 1 | Scoped pilot | Scoped rollout |
| Task, run, output, debit, audit, rerun | ✓ | ✓ | ✓ |
| GitHub issue creation | ✓ | ✓ | ✓ |
| Public API / SDK verification | — | — | — |
| Controls | |||
| Spending limits | ✓ | ✓ | ✓ |
| Approval rules and resume | ✓ | ✓ | ✓ |
| Server-side admission control | ✓ | ✓ | ✓ |
| Audit & launch readiness | |||
| Run steps and audit history | Included | Included | Included |
| DB-backed isolation testing | — | Guided | Launch checklist |
| Launch planning | — | Email guidance | Dedicated |
| Support | |||
| Support | Community | Dedicated | |
Questions, answered.
What counts as a controlled agent?
An authenticated Auza agent with credits, lifecycle status, permissions, spend rules, and audit history. The current useful tool action is GitHub issue creation.
Does Auza have a public verify API or SDK?
Not yet. Early access uses the dashboard and server routes for task runs, GitHub issue creation, approvals, reruns, and audit review.
Can Auza run outside the hosted app today?
No. The launch path is a hosted web app with Supabase, server-side GitHub App token handling, and DB-backed security checks.
What happens when a control rule blocks work?
The run stops before the model or GitHub action. If approval is required, Auza stores the exact payload and only resumes that payload after approval.
Pilot the controlled-agent flow.
Join early access for credits, GitHub issue creation, approvals, spend limits, audit, and reruns.