# Supabase — Supabase Compute: run your agents inside your project

- Company: Supabase (supabase.com)
- Announced: 2026-10-27
- Category: product-launch
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://supabase.com/blog/supabase-compute-private-alpha
- Record: https://forck.live/items/28331-supabase-compute-run-your-agents-inside-your-project
- Subject: Supabase

Supabase is launching Supabase Compute in private alpha, letting developers run agents, background jobs and APIs in the same project as their data. The company says developers told it some work does not fit in an Edge Function, because it needs more memory or CPU, runs longer than 400 seconds, or is written in another language, and that such work usually means a second platform with its own deploys and logs. Each service gets a full Linux environment and can run an AI agent, an API or web service configured with a Dockerfile, a durable job processor pulling tasks from Postgres, a data sync or embedding backfill, or a WebSocket service. Services are created with the Supabase CLI, version 2.120.0 or later, by setting compute = true under [experimental] in config.toml, picking a runtime of Node, Deno or a Dockerfile, and choosing a size of 2 GB with 1 vCPU or 4 GB with 2 vCPUs. Dreambase moved its data agent onto Compute to test it, and its Postgres queries took a median of 2.9 ms against 65 ms from another region. During the alpha Compute is limited to the us-west-2 region, is for evaluation rather than production, and may change or end; services can restart at any time, get all of the project's secrets, and have no autoscaling, GPU or persistent disk.

## Evidence

Verbatim from https://supabase.com/blog/supabase-compute-private-alpha:

> Today we're launching Supabase Compute in private alpha. Now you can run agents, background jobs, and APIs right next to your data, in the same project. During the private alpha, Compute is available in the us-west-2 region, with more regions coming soon. Join the waitlist to try it for free.
> 
> Developers told us some work doesn't fit in an Edge Function. Some work needs more memory or CPU. Some runs longer than 400 seconds, like an AI agent. Some is written in another language.
> 
> That work usually means a second platform, with its own deploys, its own logs, and debugging across two providers. Supabase Compute brings that work into your project. You pick the size, the work runs for minutes or hours, and you deploy Node, Deno, or any Dockerfile.
> 
> What you can run #
> 
> Each service gets a full Linux environment, so you can run:
> 
> An AI agent that can spin up and coordinate multiple tasks
> 
> An API or web service written in any language, configured with a Dockerfile
> 
> A durable job processor that pulls tasks from Postgres, such as OpenWorkflow
> 
> A data sync or embedding backfill that runs for hours
> 
> A WebSocket service for low-latency, real-time apps like voice agents

---

Record: https://forck.live/items/28331-supabase-compute-run-your-agents-inside-your-project
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md