Supabase Compute runs agents next to Postgres
By Steven Van ·
Private alpha is waitlist-only in us-west-2, free to try, and the announcement sets neither a later price nor a general-availability date.
On October 27, Supabase opened Compute in private alpha so agents, background jobs, and APIs can run in the same project as Postgres. Only us-west-2 projects can join.
A service is a Linux environment for an agent, a Dockerfile API, a job processor, a backfill, or a WebSocket service. It needs CLI v2.120.0 or later: set compute to true under experimental, then supabase compute new and supabase compute push. Choose 2 GB with 1 vCPU or 4 GB with 2 vCPUs, public with a URL or private with none.
The alpha is for evaluation, not production, and it may change or end. A service can restart, so save long work to Postgres, and there is no autoscaling, GPU, or persistent disk. Every service gets the project's secrets, public services suspend when idle, and private ones keep running. The free waitlist takes a Project ID for us-west-2, and the post sets no later price, no general-availability date, and no agent sandboxes.