CI, scheduling, and observability for your SQL pipelines — without the infrastructure.
SQLAnvil Cloud runs your project's pipelines for you. Open a pull request and it builds your whole workflow against a disposable branch of your database, reports pass/fail on the PR, and shows you exactly what ran. You keep authoring in your own tools; Cloud reviews, schedules, and operates.
What it actually is
SQLAnvil Cloud is a control plane, not an IDE. Authoring stays where it belongs — the CLI and your AI agents. Cloud handles the parts that need to be hosted, shared, and always-on: running CI on every change, keeping a history of every run with the SQL and errors, running things on a schedule, and doing it all without custodying your credentials.
It's built on three ideas:
Branch-aware CI
Every pull request is tested against a real, throwaway copy of your database — not a mock, not your production data.
Scale-to-zero
Runners spin up per run and disappear. Nothing idles, nothing is left billing between runs.
Zero credential custody
We broker a short-lived, revocable authorization per run. We never store your database password or service-role key.
How branch CI works
On Supabase — one pull request, start to finish, in under a minute.
You open a pull request
A webhook tells Cloud there's a change. A runner is dispatched — keyless, via workload-identity federation.
An ephemeral branch is created
Cloud mints a scoped token from your connection and creates a fresh Supabase branch of your project — an isolated copy of the schema.
Your workflow runs for real
sqlanvil run builds every model and executes every assertion against that branch.
Real objects, real data-quality checks — nothing touches production.
Results post to the PR — and the branch is destroyed
A SQLAnvil CI check turns green or red on the pull request, the run detail is captured, and the ephemeral branch is torn down so nothing is left billing.
What you get
Branch CI on every PR
Turnkey — no GitHub Action to hand-wire. Connect the repo, connect Supabase, open a PR. A status check lands on the PR automatically.
Per-action run detail
Every run shows each action's status, timing, and the exact SQL that executed. On failure, the verbatim error — with one-click Copy failure context to paste straight into an AI agent for a fix.
Scheduled runs & Workflows
Run a tag/action selection of the graph on a cron — with dependency options and a target environment — from the dashboard, no cron server of your own.
Credential brokering
Connect Supabase once via OAuth. Cloud stores only an encrypted, revocable refresh token and mints a fresh 1-hour token per run. Revoke it anytime.
Supabase hosted, others BYO
Hosted branch CI runs on Supabase today. Postgres, BigQuery, and MySQL run in your own CI and report back with an ingest token — same history, same PR checks.
Your warehouse, your account
Runs execute against your database — compute and storage stay on your bill. Cloud is the thin, always-on layer on top, which is why it can stay lean.
Remote MCP server
Point Claude Code — or any MCP client — at your project with one token. Your agent can list runs, pull full failure context, inspect the graph, and trigger workflows: the operational state it needs to debug and operate your pipelines.
Code workspace
Browse any branch of your repo in the dashboard — syntax-highlighted source, compiled-results preview, and an interactive DAG graph of your workflow. Read-only by design: authoring stays in your own tools.
We broker credentials — we don't hold them.
The honest version of "zero custody": SQLAnvil Cloud never requests or stores your database password or service-role key. It holds one thing — a Supabase OAuth refresh token, encrypted at rest, that you can revoke at any time. Each run gets a short-lived access token minted from it; the raw branch credentials exist only for the seconds a run is executing, then are destroyed with the branch.
Who it's for
- Teams (and solo builders with agents) running SQLAnvil pipelines on Supabase or Postgres.
- Anyone who wants tested pull requests against a real database without standing up CI infra.
- Security-conscious shops that can't hand a SaaS their warehouse credentials.