Comparison

Stolon and Supabase

Supabase is a platform around Postgres, and its branches are environments for schema changes. A Stolon branch carries the whole database, and its data merges back.

As of 26 September 2026.

	Supabase	Stolon
What it is	a Postgres development platform: a dedicated Postgres plus auth, storage, realtime and generated APIs (Apache-2.0)	a Postgres-compatible database; closed source
A branch	a separate environment with its own instance and API credentials; by default it starts with no data from the main project (seed files, or an "include data" option)	`CREATE DATABASE b`: the whole database, schema, rows and history, instantly
Merging a branch back	merging runs a deployment workflow that applies the branch's pending migrations to production; the branching guide describes no data merge	`MERGE DATABASE b INTO main`: rows and schema, with conflicts named `table[pk].column`
Going back in time	daily backups kept 7 days on Pro, 14 on Team; point-in-time recovery $100 per month per 7 days of retention	`FOR SYSTEM_TIME AS OF` on any table and branch, and restore a branch to a moment
Branch price	$0.01344 per branch, per hour	no per-branch fee on paid plans
Plans	Free $0 (2 active projects, 500 MB database, paused after a week idle); Pro $25/month (8 GB disk included, then $0.125 per GB); Team $599/month; Enterprise custom	free in preview; prices published at launch
Postgres surface	PostgreSQL itself, with extensions	Postgres-compatible, with pgvector and the common extensions (check your queries)

When each fits

Supabase if you want the platform (auth, storage, realtime and APIs) with branches as preview environments.
Stolon if what you branch is the data: an agent's writes, a backfill or a migration, merged back after review.

Sources

supabase.com/pricing: plans, branching, disk, backups and PITR prices
supabase.com/docs/guides/deployment/branching: what a branch is, its data, how it merges
github.com/supabase/supabase: description and license
Stolon: docs