Skip to content
Private Alpha

Computefor agentic workloads

Agent sandboxes and always-on backend services running inside your Supabase project — next to your data, behind your auth.

Join the waitlist
Workloads

One runtime,two shapes of work

Sandboxes, APIs, and background jobs usually mean three vendors and a database somewhere else. Compute runs them all in Supabase alongside your application backend.

Sandboxes

Isolated environments for agent code

Execute code in a secure, isolated environment — one per task, per session, or per agent.

  • Per-session environment for executing code
  • Provision programmatically via the API or MCP server
  • Suspend and resume with state preserved
Services

Always-on backends in any language

Transcription pipelines, embedding jobs, agent frameworks, and APIs — running as long as the work takes.

  • Auto-scaling for traffic surges
  • No wall-clock limits on execution
  • Any runtime, static binary, or Dockerfile
  • HTTP services, background jobs, and long-running pipelines
A diagram showing humans and agents connecting to Supabase Compute. Two always-on backend services serve the application; agents spin up short-lived sandboxes on demand, which build, run, and suspend automatically.

  • One primitive, every workload

    Ephemeral sandboxes and always-on HTTP services, one primitive.

  • Any language

    Node, Deno, or any Dockerfile.

  • Next to your database

    Same network as Postgres — single-digit millisecond queries.

  • Scale to zero

    Services suspend when idle and resume in under a second. You pay nothing while they sleep.

Security

One trust boundary,preconfigured

Every sandbox and service inherits your project's auth, roles, and permissions the moment it starts, running in its own microVM with dedicated CPU and memory. Agents get a sandbox that is already scoped to the data it is allowed to touch — nothing more.

Short-lived credentials

Access runs through Supabase Auth with short-lived keys, not standing secrets.

Zero-config data access

Reach your database and Storage with the permissions your key already carries.

Per-workload firewalls

Define which external endpoints and ports each workload can reach.

Cloaked secrets

Scope secrets per workload, and cloak values so your code never sees them.

Patched automatically

Kernel-level security patches roll out automatically. Nothing to do on your part.

Dependency scanning

Dependencies are scanned at runtime, with alerts as new vulnerabilities land.

Deployment

Deploy fromwherever you work

The same deployment surface serves humans and agents: one command in a terminal, one tool call in an agent session, one request against the API.

Join the waitlist
Terminal

Frequently asked questions

Run your next workloadnext to your data

Compute is in Private Alpha. Join the waitlist and we'll reach out as invites roll out.

By submitting this form, you acknowledge that Supabase Compute is offered as a private alpha preview, provided on an "as is" and "as available" basis without warranties of any kind. It is intended for internal evaluation only and should not be used to serve production workloads or your own end customers. Supabase may modify, suspend, or discontinue the preview at any time without notice, and there is no guarantee it will become a generally available product. You confirm you are authorized to submit this request on behalf of your organization, and that you have read and understood our Privacy Policy.