--- title: Supabase Compute: run your agents inside your project description: Supabase launched Compute in private alpha, letting developers run agents, background jobs, and APIs inside their Supabase project. It targets work that... canonical: https://daily.dev/posts/supabase-compute-run-your-agents-inside-your-project-jhh9tg0xx twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Supabase Compute: run your agents inside your project | daily.dev og:description: Supabase launched Compute in private alpha, letting developers run agents, background jobs, and APIs inside their Supabase project. It targets work that... og:url: https://daily.dev/posts/supabase-compute-run-your-agents-inside-your-project-jhh9tg0xx og:image: https://api.daily.dev/og/posts/JhH9TG0xx.png og:image:alt: Supabase Compute: run your agents inside your project og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Supabase Compute: run your agents inside your project **[Supabase](https://daily.dev/sources/supabase)** · 3 min read · 1 upvotes · 0 comments ## Summary Supabase launched Compute in private alpha, letting developers run agents, background jobs, and APIs inside their Supabase project. It targets work that doesn't fit an Edge Function: jobs needing more memory or CPU, runs longer than 400 seconds, or code in another language. Compute is available only in us-west-2 for now, and you deploy Node, Deno, or any Dockerfile with sizes of 2 GB with 1 vCPU or 4 GB with 2 vCPUs. Dreambase moved a data agent onto Compute to test it, and its Postgres queries took a median of 2.9 ms versus 65 ms from another region. The alpha has no autoscaling, GPU, or persistent disk, and a service can be restarted at any time. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I run a long-running AI agent or background job on Supabase without using a separate hosting platform? Supabase Compute, launched in private alpha, lets you run agents, background jobs, and APIs inside your Supabase project. It supports Node, Deno, or any Dockerfile, with services sized at 2 GB/1 vCPU or 4 GB/2 vCPUs, running for minutes or hours instead of the 400-second limit on Edge Functions. It is currently limited to the us-west-2 region. _Developers evaluating ways to colocate agents with their database can track Supabase Compute updates on daily.dev._ ### What CLI version do I need to deploy a service with Supabase Compute? You need Supabase CLI version 2.120.0 or later. After enabling compute = true under [experimental] in supabase/config.toml, you create a service with 'supabase compute new', choose a runtime and size, replace the starter code in supabase/compute/, and deploy with 'supabase compute push'. _Teams adopting new Supabase CLI features can keep their toolchain current via daily.dev._ ### How much faster are database queries when an agent runs inside the same project as its Postgres database versus a separate region? Dreambase moved its data agent onto Supabase Compute and measured a median query latency of 2.9 milliseconds to Postgres, compared to 65 milliseconds when the agent ran from another region, according to their test during the Compute private alpha. _Developers weighing colocated compute versus cross-region hosting can follow real benchmarks like this on daily.dev._ ## Similar posts on daily.dev - [Build anything: Supabase from code, and an MCP server for your app](https://daily.dev/posts/build-anything-supabase-from-code-and-an-mcp-server-for-your-app-57ek84lkt) · Supabase · 17 upvotes · 0 comments - [Announcing PostgreSQL for agents in AlloyDB](https://daily.dev/posts/announcing-postgresql-for-agents-in-alloydb-dyzuabrfv) · Google Cloud · 2 upvotes · 0 comments - [Agents have their own computers with Sandboxes GA](https://daily.dev/posts/agents-have-their-own-computers-with-sandboxes-ga-bvcsfels6) · Cloudflare · 3 upvotes · 0 comments - [Runtime instances: persistent compute for production AI agents on Amazon Bedrock AgentCore](https://daily.dev/posts/runtime-instances-persistent-compute-for-production-ai-agents-on-amazon-bedrock-agentcore-ex8xt1xhg) · AWS · 2 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#backend](https://daily.dev/tags/backend), [#docker](https://daily.dev/tags/docker), [#postgresql](https://daily.dev/tags/postgresql), [#supabase](https://daily.dev/tags/supabase) [View this post on daily.dev](https://daily.dev/posts/supabase-compute-run-your-agents-inside-your-project-jhh9tg0xx) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Supabase Compute: run your agents inside your project","url":"https://daily.dev/posts/supabase-compute-run-your-agents-inside-your-project-jhh9tg0xx","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/supabase-compute-run-your-agents-inside-your-project-jhh9tg0xx"},"datePublished":"2026-10-27T16:06:49.367Z","dateModified":"2026-10-27T17:55:13.338Z","description":"Supabase launched Compute in private alpha, letting developers run agents, background jobs, and APIs inside their Supabase project. It targets work that...","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","isAccessibleForFree":true,"articleSection":"Supabase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Supabase","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/d0aa77cfb88d44dd8e6d5cd02fdf80bd","url":"https://daily.dev/sources/supabase"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/supabase-compute-run-your-agents-inside-your-project-jhh9tg0xx","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,backend,docker,postgresql,supabase","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Supabase","item":"https://daily.dev/sources/supabase"},{"@type":"ListItem","position":3,"name":"Supabase Compute: run your agents inside your project"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/supabase-compute-run-your-agents-inside-your-project-jhh9tg0xx#faq","mainEntity":[{"@type":"Question","name":"How do I run a long-running AI agent or background job on Supabase without using a separate hosting platform?","acceptedAnswer":{"@type":"Answer","text":"Supabase Compute, launched in private alpha, lets you run agents, background jobs, and APIs inside your Supabase project. It supports Node, Deno, or any Dockerfile, with services sized at 2 GB/1 vCPU or 4 GB/2 vCPUs, running for minutes or hours instead of the 400-second limit on Edge Functions. It is currently limited to the us-west-2 region. Developers evaluating ways to colocate agents with their database can track Supabase Compute updates on daily.dev."}},{"@type":"Question","name":"What CLI version do I need to deploy a service with Supabase Compute?","acceptedAnswer":{"@type":"Answer","text":"You need Supabase CLI version 2.120.0 or later. After enabling compute = true under [experimental] in supabase/config.toml, you create a service with 'supabase compute new', choose a runtime and size, replace the starter code in supabase/compute/, and deploy with 'supabase compute push'. Teams adopting new Supabase CLI features can keep their toolchain current via daily.dev."}},{"@type":"Question","name":"How much faster are database queries when an agent runs inside the same project as its Postgres database versus a separate region?","acceptedAnswer":{"@type":"Answer","text":"Dreambase moved its data agent onto Supabase Compute and measured a median query latency of 2.9 milliseconds to Postgres, compared to 65 milliseconds when the agent ran from another region, according to their test during the Compute private alpha. Developers weighing colocated compute versus cross-region hosting can follow real benchmarks like this on daily.dev."}}]} ```