dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-05 09:25:06 +03:00

Files

T

Francesco Sansalvadore 4617b6f4cb feat: compute landing page (#50899 )

Compute landing page.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* Added a Compute product page introducing ephemeral sandboxes and
always-on HTTP services, with information on workloads, security,
deployment, and common questions.
* Added a private-alpha waitlist form with submission confirmation and
error feedback.
* Added Compute links and a “Private Alpha” badge in product navigation
and the footer.
* Added an animated diagram illustrating Compute workloads and their
lifecycle.
* **Documentation**
* Added a Compute overview covering runtimes, scaling, security,
deployment, and availability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-10-02 16:14:13 +02:00

2.5 KiB

Raw Permalink Blame History

Supabase Compute

Run AI-agent sandboxes and production backends on one runtime, next to your database. Now in Private Alpha.

Supabase Compute is a fully managed compute service built for agentic development. Use it as a sandbox platform offering short-lived, isolated environments to execute code, or as a place to run always-on HTTP services written in any language. Everything runs in the same region and network as your primary Postgres database.

Key Features

Two workload shapes: ephemeral sandboxes for untrusted code and always-on HTTP services, on one runtime
Any language: Node, Deno, or any Dockerfile in Private Alpha — no wrapper scripts or glue code
Next to your database: same region and network as Postgres, with single-digit-millisecond queries
Scale to zero: idle sandboxes and services suspend automatically and resume in under a second
No wall-clock limits: jobs and pipelines run as long as the work takes
Preconfigured trust boundary: access control via Supabase Auth with short-lived credentials; workloads reach the database and Storage with the permissions carried by their key
Per-workload firewalls: define which external endpoints and ports each sandbox or service can reach
Cloaked secrets: scope secrets per workload; optionally have Supabase inject values only on requests to approved services
Automatic patching and dependency scanning: kernel security patches applied automatically; runtime alerts for newly disclosed vulnerabilities
Safe releases: branching, progressive rollouts, automatic rollback on bad deploys, and auto-scaling
Built-in observability: execution logs, traces, audit logs, and usage metrics in the Supabase dashboard

Deployment

Supabase CLI: supabase compute deploy
MCP server: agents provision and manage sandboxes and services programmatically
Management API: script deployments from any environment
GitHub Actions: ready-made CI/CD workflows
Compute skill: teach your coding agent the full surface

Common Use Cases

Sandboxes for AI agents executing untrusted code
Agent frameworks and long-running agent sessions
Transcription, embedding, and data pipelines without runtime limits
Always-on HTTP APIs and backend services
Background jobs and scheduled work
MCP server hosting

Availability

Compute is in Private Alpha behind a waitlist. Existing Edge Functions keep running unchanged; because Compute supports the Deno runtime, functions can migrate as-is when you choose.

2.5 KiB Raw Permalink Blame History