Pricing
Priced per project and run volume — seats are always free. Built for the agent-native era, not the IDE era.
Just want it free? The open-source SQLAnvil CLI is free forever — Cloud is the managed control plane on top.
Free trial
Try hosted Cloud. During early access there’s no time limit — everything is free.
- 1 project
- Unlimited seats
- Branch CI on every pull request
- Full run detail + Copy-for-AI
- No card required
- Then pick Pro or Enterprise
Pro
For teams shipping pipelines daily. Seats always free.
- Everything in Free, plus:
- Unlimited projects (billed per project)
- 5,000 run-minutes / mo (fair use) planned
- Scheduled Workflows
- Failure alerts (email + Slack) planned
- Multiple environments
- 30-day run history
Business
For teams running many projects — unlimited projects and higher limits.
- Everything in Pro, plus:
- Unlimited projects (flat rate)
- 25,000 run-minutes / mo planned
- Team roles & permissions planned
- Priority run queue planned
- 90-day run history planned
- Webhooks & API access planned
Enterprise
Zero-custody credentials, governance, and scale — on a custom contract.
- Everything in Pro, plus:
- Keyless / BYO-vault credential tiers planned
- SSO, RBAC & audit logs planned
- Dedicated runners planned
- SLA & support arrangements
- Custom retention & run volume
dbt charges $100–$400 per developer seat. SQLAnvil prices per project and run volume, so adding teammates — or agents — never costs more.
Compare all features
planned = on the roadmap, not shipped yet. Everything else is live today.
| Features | Trial | Pro | Business | Enterprise |
|---|---|---|---|---|
| Usage & limits Limits are the planned shape — nothing is metered or enforced during early access. | ||||
| Plan length | 14-day trial | Monthly | Monthly | Annual |
| Projects | 1 | Per project | Unlimited | Unlimited |
| Seats / users | Unlimited | Unlimited | Unlimited | Unlimited + SSO |
| Connected warehouses | 1 | 3 | Unlimited | Unlimited |
| Run-minutes | 500 total | 5,000 / mo | 25,000 / mo | Custom |
| Concurrent runs | 1 | 2 | 5 | Custom |
| Environments | 1 | Multiple | Unlimited | Unlimited |
| Scheduled workflows | — | 5 | Unlimited | Unlimited |
| Run-history retention | 7 days | 30 days | 90 days | Custom |
| Branch CI | ||||
| Branch CI on pull requests | ✓ | ✓ | ✓ | ✓ |
| Ephemeral Supabase branches (create → run → destroy) | ✓ | ✓ | ✓ | ✓ |
| SQLAnvil CI status check on the PR | ✓ | ✓ | ✓ | ✓ |
| Automatic branch cleanup | ✓ | ✓ | ✓ | ✓ |
| Per-action run detail | ✓ | ✓ | ✓ | ✓ |
| Executed-SQL capture | ✓ | ✓ | ✓ | ✓ |
| Copy failure context (AI-ready bundle) | ✓ | ✓ | ✓ | ✓ |
| Workflows & scheduling | ||||
| Scheduled Workflows (cron) | — | ✓ | ✓ | ✓ |
| Tag & action selection | — | ✓ | ✓ | ✓ |
| Include dependencies / dependents | — | ✓ | ✓ | ✓ |
| Run on demand ("Run now") | — | ✓ | ✓ | ✓ |
| Pinned releases (frozen compilations) | — | ✓ | ✓ | ✓ |
| Priority run queue planned | — | — | ✓ | ✓ |
| Operate & debug | ||||
| Remote MCP server (operate from your coding agent) | ✓ | ✓ | ✓ | ✓ |
| Code workspace (read-only browse + results preview) | ✓ | ✓ | ✓ | ✓ |
| DAG graph of the workflow | ✓ | ✓ | ✓ | ✓ |
| Failure alerts — email planned | — | ✓ | ✓ | ✓ |
| Failure alerts — Slack planned | — | ✓ | ✓ | ✓ |
| Outbound webhooks planned | — | — | ✓ | ✓ |
| REST API access planned | — | — | ✓ | ✓ |
| Warehouses | ||||
| Supabase — hosted branch CI | ✓ | ✓ | ✓ | ✓ |
| Postgres — BYO compute (ingest token) | ✓ | ✓ | ✓ | ✓ |
| BigQuery — BYO compute (ingest token) | ✓ | ✓ | ✓ | ✓ |
| MySQL / MariaDB — BYO compute (ingest token) | ✓ | ✓ | ✓ | ✓ |
| Cross-warehouse FDW / bridge | ✓ | ✓ | ✓ | ✓ |
| Credentials & security | ||||
| OAuth credential brokering (zero DB-cred custody) | ✓ | ✓ | ✓ | ✓ |
| Encrypted, revocable per-run tokens | ✓ | ✓ | ✓ | ✓ |
| Team roles & permissions planned | — | — | ✓ | ✓ |
| Keyless / BYO-vault credential tiers planned | — | — | — | ✓ |
| SSO (SAML / OIDC) planned | — | — | — | ✓ |
| Audit logs planned | — | — | — | ✓ |
| Support | ||||
| Docs & GitHub community (fully self-service) | ✓ | ✓ | ✓ | ✓ |
| SLA planned | — | — | — | ✓ |
| Onboarding assistance planned | — | — | — | ✓ |
What you bring
SQLAnvil Cloud is the control plane — your warehouse compute and storage stay on your own account. Here's what you provide:
A data warehouse
A Supabase project for hosted branch CI (Pro plan — branching requires it), or Postgres, BigQuery, or MySQL for BYO-compute runs. SQLAnvil runs against your warehouse — you own the compute and storage.
A GitHub repository
Where your SQLAnvil project lives. Connect it once; every pull request triggers a branch-CI run and gets a status check back.
A SQLAnvil project
A workflow_settings.yaml + definitions/ folder, authored with the free open-source SQLAnvil CLI. New to it? Follow the Cloud getting-started guide.
Non-Supabase warehouses (Postgres / BigQuery / MySQL) run in your own CI (e.g. GitHub Actions) and report back with an ingest token — SQLAnvil never holds write credentials. Hosted execution is Supabase-only for now.