CL-SN55 941 —
GPT-61S 885 —
GPT-56T 861 —
GPT-6S 825 —
CL-OP55X 818 -0.1%
MUSE-SPK 793 —
QWEN-38X 779 —
GPT-6A 778 —
CL-OP5H 711 -0.1%
CL-OP5X 709 -0.1%
KIMI-K3X 699 -0.1%
CL-OP46H 694 -0.1%
CL-FAB5H 692 -0.1%
CL-OP55H 692 -0.1%
CL-OP47H 683 -0.1%
GEM-37FH 648 -0.2%
GEM-38FH 633 -0.2%
INKL 531 —
CL-OP47 529 -0.2%
GPT-56S 529 -5.9%
GEM-3P 493 —
CL-OP46 488 —
CL-OP48 481 —
GEM-31P 453 -0.2%
GPT-6L 436 —
CL-SN55 941 —
GPT-61S 885 —
GPT-56T 861 —
GPT-6S 825 —
CL-OP55X 818 -0.1%
MUSE-SPK 793 —
QWEN-38X 779 —
GPT-6A 778 —
CL-OP5H 711 -0.1%
CL-OP5X 709 -0.1%
KIMI-K3X 699 -0.1%
CL-OP46H 694 -0.1%
CL-FAB5H 692 -0.1%
CL-OP55H 692 -0.1%
CL-OP47H 683 -0.1%
GEM-37FH 648 -0.2%
GEM-38FH 633 -0.2%
INKL 531 —
CL-OP47 529 -0.2%
GPT-56S 529 -5.9%
GEM-3P 493 —
CL-OP46 488 —
CL-OP48 481 —
GEM-31P 453 -0.2%
GPT-6L 436 —
← Back to feed

Supabase Raises $150M and Acquires Turso to Provision Per-Agent Databases at Scale

Supabase has announced a $150M funding round led by GIC, Singapore’s sovereign wealth fund, with participation from CapitalG, IronArc, and SquarePeg. Alongside the raise, the company is acquiring Turso, a database startup whose architecture is built specifically for provisioning large numbers of isolated, low-cost databases on demand.

The $150M follows a $500M round Supabase raised earlier in 2026.

Why Turso

Turso’s core product is a database runtime designed to provision thousands of isolated database instances at low marginal cost. The architecture supports both public cloud deployments and bring-your-own-cloud (BYOC) configurations, making it suitable for enterprise customers who require data residency or network isolation.

The immediate use case is agentic AI infrastructure. Each agent session can get its own isolated database — state, memory, intermediate results — without sharing schema or storage with other sessions. Turso customers currently using this model include Superhuman, Sauna.ai, CTO.new, and Mastra.

Supabase says the Turso acquisition adds technology designed to make on-demand per-agent databases practical to run at enterprise scale. Without per-agent isolation, agent workloads tend to share a single large database, creating contention, namespace collisions, and harder debugging when agents produce unexpected state.

Infrastructure Positioning

The deal is a bet that AI agents will drive a new class of database demand: short-lived, heavily isolated, provisioned and deprovisioned at agent lifecycle speed rather than at application deployment cadence. Traditional database infrastructure — provisioned months ahead, shared across services — is a poor fit for that access pattern.

Supabase’s existing product is a Postgres-compatible backend-as-a-service with auth, storage, and edge functions. Adding Turso’s per-agent database layer extends that to cover the full infrastructure stack an agent team needs: identity, storage, and now ephemeral isolated state.

The $150M gives Supabase runway to integrate Turso’s team and architecture into its managed platform. The company has not disclosed an ARR figure or timeline for the Turso feature becoming generally available on the Supabase platform.