Shipcel vs Supabase

Supabase is a backend: Postgres with sign-in, row-level security, realtime and Edge Functions, but not your frontend. Shipcel deploys your whole app, frontend and API, into your Cloudflare account, with D1 (SQLite) databases, R2 file storage, KV, and a sign-in and realtime service that runs in the same account. The main differences are Postgres versus SQLite, how access rules are written, and where everything runs. Many apps can use both: Shipcel for hosting, Supabase for data.

Which one fits

Choose Shipcel if

You want your frontend, API, database and files in one account and on one bill.
Your data fits SQLite: D1 databases hold up to 500 MB each on the free plan and 10 GB on Workers Paid.
You run several small apps: Supabase Free allows 2 active projects and Pro adds about $10 a month of compute per extra project; on Cloudflare each extra app and database costs nothing beyond its usage.
You don’t want projects paused for inactivity: Workers and D1 databases don’t sleep.
You serve many files: R2 has no egress fees, while Supabase Pro charges $0.09 per GB of uncached egress beyond 250 GB.
You want sign-in and realtime without a monthly-user quota: passkey, GitHub, Google and email sign-in and realtime channels run in your account and count against Cloudflare’s request allowances.

Choose Supabase if

You need Postgres: extensions such as PostGIS and pgvector, complex queries, or an existing Postgres schema.
You need phone sign-in, access rules written as Postgres policies, or a realtime stream of every database change. Shipcel’s rules are set per table (everyone, signed-in users or each row’s owner), and its realtime carries the changes made through its data API.
You want a spreadsheet-style table editor and GraphQL over your data. Shipcel has a table browser, a SQL console and a REST data API, but no GraphQL.
You want to self-host the same stack: Supabase is open source and runs with Docker Compose.

Side by side

Free plans
	Shipcel + Cloudflare free plans	Supabase Free
Price	$0	$0
Projects	Up to 100 Shipcel projects; up to 10 D1 databases per account	2 active projects (paused ones don’t count)
Database	D1 (SQLite): 500 MB per database, 5 GB in total; 5 million rows read and 100,000 written a day	Postgres: 500 MB per project, read-only above that
File storage	R2: 10 GB, 1 million writes and 10 million reads a month (R2 is added through a checkout that needs a payment method)	1 GB; uploads up to 50 MB
Egress	No egress fees for static files or R2	5 GB uncached and 5 GB cached a month
Inactivity	Nothing pauses	Paused after a week of low activity; restorable for a year
Backups	Point-in-time restore for 7 days	Not included
Sign-in	Included: passkeys, GitHub and Google. No monthly user limit; a sign-in uses about 5 to 7 of your 100,000 daily Worker requests	50,000 monthly active users
Realtime	Included: channels with presence and broadcast on Durable Objects. Connections and incoming messages count toward 100,000 requests a day; messages to listeners are free and idle connections hibernate	200 concurrent connections, 2 million messages a month
When you exceed it	Requests fail until midnight UTC; nothing is billed (R2 bills beyond its free tier)	Never billed; restrictions after a notice and grace period

Paid plans
	Shipcel + Cloudflare Workers Paid	Supabase Pro
Base price	$5 a month per Cloudflare account; Shipcel $0	$25 a month per organization, with $10 of compute credit (one Micro project)
Each extra project	No fixed fee; usage only	About $10 a month of Micro compute ($0.01344 an hour)
Database storage	D1: 5 GB included, then $0.75 per GB-month; up to 10 GB per database	8 GB of disk per project, then $0.125 per GB-month
File storage	R2: 10 GB free, then $0.015 per GB-month	100 GB included, then $0.0213 per GB-month
Egress	None for static files or R2	250 GB uncached included, then $0.09 per GB; 250 GB cached, then $0.03 per GB
Backups	Point-in-time restore for 30 days, included; scheduled copies in R2 at R2’s storage price	Daily backups kept 7 days; point-in-time recovery from about $100 a month
Spending control	No hard cap from Cloudflare. Shipcel’s budget guard alerts over a budget ($0 by default) and can pause the app; Cloudflare’s budget alerts email you	Spend cap on by default for usage items; compute and add-ons are always billed

Features
	Shipcel	Supabase
Hosts your frontend	Yes: static files and server code on Workers	No; Edge Functions only
SQL database	D1 (SQLite)	Postgres with extensions
Sign-in	Passkeys, GitHub, Google, email links and passwords, as standard OpenID Connect; no phone	Yes, including email and password, magic links, phone, and passkeys in beta
Row-level security	Per table, through the data API: everyone, signed-in users or each row’s owner	Yes, as Postgres policies
Realtime	Channels with presence and broadcast on Durable Objects, and the changes made through the data API	Broadcast, presence and database changes
File storage	R2, S3-compatible, with a file browser for uploads (up to 25 MB), downloads and deletions	Supabase Storage, S3-compatible
Server code	Workers in JavaScript, TypeScript or Python; containers on Workers Paid	Edge Functions in TypeScript (Deno-compatible)
Preview environments	Every branch and pull request (Cloudflare Worker Previews, beta), on staging copies of your data	Branching on paid plans: a database per pull request at $0.01344 per branch-hour
Rollback	One click for code; point-in-time restore for databases	Point-in-time recovery is a paid add-on; Free has no backups
Table and SQL editor	A table browser and SQL console, with a restore point before each change	Table Editor and SQL Editor in Studio, on Free

What it costs

Five side projects with databases

Five small apps, each with its own database and light traffic.

Monthly cost
Setup	Per month	How it adds up
Vercel Hobby + Supabase Pro	$65	Vercel Hobby: $0, for non-commercial use only. Supabase Free allows 2 active projects, so five need Pro: $25 with one Micro database, plus about $10 for each of the other four.
Shipcel + Cloudflare	$0	Shipcel: $0. Cloudflare’s free plan: five Workers and five D1 databases (up to 10 per account), each under 500 MB.

Assumptions: Each app stays within Cloudflare’s free daily limits. Supabase bills Micro compute at $0.01344 an hour, about $10 a month per project, and Pro includes $10 of compute credit.

$0 instead of $65 a month. On Supabase Free you could keep two of the five, and they pause after a week of low activity.

An app serving 1 TB of downloads a month

A product stores 100 GB of files and serves 1 TB of downloads a month.

Monthly cost
Setup	Per month	How it adds up
Supabase Pro Storage	$47.50 to $92.50	$25 base fee; 100 GB of files included. Egress: 250 GB included; the other 750 GB costs $0.03 per GB from Supabase’s CDN cache ($22.50) or $0.09 per GB uncached ($67.50).
Cloudflare R2	$1.35	Storage: 90 GB beyond the free 10 GB × $0.015 = $1.35. Egress: $0, because R2 has no egress fees. Reads: about 1 million downloads, inside the 10 million free reads a month.

Assumptions: An average file of 1 MB. Storage costs only; the app’s own compute is separate on both.

About $1.35 a month instead of $47.50 to $92.50 for the same files and downloads.

Billing and surprise-bill protection

Supabase Free is never billed: over quota you get a notice and a grace period, then restrictions such as read-only databases.
Supabase Pro’s spend cap is on by default and blocks usage items (disk, egress, monthly active users, storage, function invocations, realtime) at the plan quota. Compute for every project and add-ons such as point-in-time recovery, custom domains and IPv4 are always billed, so the total bill isn’t capped.
Cloudflare’s free plan is never billed for Workers, D1 or KV: over a daily limit, requests and queries fail until midnight UTC. R2 file storage bills usage beyond its free tier (never egress).
Workers Paid ($5 a month per account) has no hard spending cap. Budget alerts email you when usage passes an amount ($10 by default) but don’t stop anything; per-Worker CPU and subrequest limits can stop runaway code. Shipcel’s budget guard alerts over each app’s budget ($0 by default) and can pause the app, minutes after the budget is crossed.

Moving from Supabase

You can keep Supabase for data, and sign-in if you prefer it, and use Shipcel only for hosting: your Worker calls Supabase over HTTPS like any client.
Moving data from Postgres to D1 means converting the schema to SQLite: types, defaults and functions differ, and row-level security policies become the data API’s per-table rules (everyone, signed-in users or each row’s owner) or checks in your own code.
Both stores are S3-compatible, so tools such as rclone can copy files from Supabase Storage to R2.

Sources

Checked 8 October 2026. Prices change; confirm on each provider's page before you decide.