What the price buys
Most small products start at $7 to $14.
Every price below includes the database. A static frontend is the cheapest way to ship: a React, Vue, or Svelte app talks to your Postgres database and Auth directly, so a real web service needs no server to run.
Compute is where your own API lives. A web or mobile app calls it with the signed-in user’s token, so the database password never leaves the backend. Next.js runs there too.
Servers are in the United States. That is how the price stays low. Read why.
| You build | What runs | Monthly total, database included |
|---|---|---|
| A static web app | A React, Vue, or Svelte single-page app (a Vite build), hosted free, with PostgreSQL, Auth, and an automatic REST API. Sign-in, per-user data, forms, dashboards. | $7 Hobby |
| A Go API | A lightweight Go service, plus the same database and Auth. Pair it with a static frontend. | $14 Hobby $7 + Compute 1 GB $7 |
| A Rust API | A lightweight Rust service (a static binary), plus the same database and Auth. Pair it with a static frontend. | $14 Hobby $7 + Compute 1 GB $7 |
| A Python (FastAPI) API | A lightweight FastAPI service (uvicorn), plus the same database and Auth. Pair it with a static frontend. | $14 Hobby $7 + Compute 1 GB $7 |
| A Next.js app | Next.js (standalone) running on Compute, with server rendering and API routes, plus the same database and Auth. | $14 Hobby $7 + Compute 1 GB $7 |
Hobby is sized for small products: 0.5 vCPU (shared by the database and the API), 1 GB, 4 GB database. It comfortably runs a side project or an MVP with thousands of daily users. In our benchmark (pgbench, on the kind of server we run, with the server otherwise idle) a Hobby database connected to directly handled about 200 read/write transactions per second (pgbench's TPC-B-like test: five statements in each transaction) and about 700 read-only ones (and about 600 read-only ones each with 64 databases on the same server all running flat out at once); through the API, which is what supabase-js uses, about 200 reads or 300 updates per second (of one row, by its key). Real results depend on your queries and on how busy the server is. Outbound transfer is included up to each plan's limit (see the table below), and there is no limit or charge for the number of users. Beyond the included amount, outbound transfer is $0.05 per GB on every plan, and you can set a monthly limit on that charge.
Plans that grow in clear steps
Pick the footprint
your project needs.
Every plan includes Auth, static frontend hosting, daily backups with seven-day retention, Point-in-Time Recovery, and the option to add managed Valkey. Realtime is included in every plan and is switched on per project when you need it. Project memory is the total resource envelope for the project services; it is not database memory alone. CPU is shared by PostgreSQL, Auth, and REST. Database disk includes the write-ahead log and temporary files. Included egress is project-wide, including Compute and other project services.
| Plan | Project memory | Shared CPU (database and API) | Database disk | Project egress | Monthly price | Realtime | Point-in-Time Recovery |
|---|---|---|---|---|---|---|---|
| Hobby | 1 GB | 0.5 vCPU | 4 GB | 250 GB / month | $7 | Included | Included |
| Larger | More memory and CPU: larger plans, and for heavy workloads a whole server of your own as the database host of your organization (no neighbours, no CPU overcommit). Planned, and not available yet. Tell us what you need: hello@koedodb.com. | ||||||
Hobby is the starting plan. The free trial starts every new project at Hobby for 30 days, with Compute and Valkey included free for the trial too. Outbound transfer (the API, Functions, static sites and apps; direct database connections are not counted) beyond what a plan includes is $0.05 per GB, and you set a monthly limit on that charge; we tell you at 80% and 100%. Users are never counted or billed.
Speed
What a database
does on each plan.
Measured with one database on a machine of that size, with the API and the database sharing the CPU. Transactions or requests per second. Your queries and load will differ.
| Hobby | 1 vCPU · 2 GB | 2 vCPU · 4 GB | |
|---|---|---|---|
| Status | Available | Planned | Planned |
| TPC-B-like transactions (reads and writes) | ~200 | ~1,000 | ~2,000 |
| Read-only transactions | ~700 | ~10,000 | ~22,000 |
| Update one row by its key | ~290 | ~2,400 | ~3,500 |
| API: read one row by its key | ~200 | ~900 | ~1,400 |
| API: update one row by its key | ~300 | ~700 | ~1,100 |
The database is measured with pgbench, the API with a load tool. The bigger plans are measured on test machines of that size and are not available yet.
Compute and Functions
Add Compute,
pay for its size.
Static frontend hosting and Functions come with every project. Compute is a long-running service: bring a container image in any language (Go, FastAPI, Rust, Next.js and so on), priced by the CPU and memory it gets. Pick the size your app needs; each tier doubles the one before it.
| Compute size | Shared CPU | Memory | Good for | Monthly price |
|---|---|---|---|---|
| Compute 1 GB | 0.5 vCPU shared | 1 GiB | A Go, FastAPI or Rust API, or a Next.js app (standalone) | $7 |
| Compute 2 GB | 1 vCPU shared | 2 GiB | A busier Next.js app or API | $14 |
| Compute 4 GB | 2 vCPU shared | 4 GiB | A heavy app or several services in one | $28 |
CPU is shared with other projects and can burst above the figure when the server is idle. Functions run with 384 MiB of memory per project. During the free trial Compute is included at no extra cost.
A focused starting point
Compare the price
of a production start.
KoedoDB is designed for smaller independent projects. Supabase offers a broader platform and materially more included capacity on its Pro plan; KoedoDB starts with a smaller, predictable project footprint.
| At comparable tiers | KoedoDB Hobby | Supabase Pro |
|---|---|---|
| Full-stack total (DB + Auth + Compute) | $14 / month Hobby $7 + Compute 1 GB $7 | $45 / month Pro $25 + Vercel Pro $20 |
| Starting price | $7 / project / month after a 30-day free trial | $25 / organization / month first Micro compute instance included |
| CPU | 0.5 vCPU (shared) | Shared (core count not published) |
| Memory | 1 GB | 1 GB |
| Database included | 4 GB database (write-ahead log included) | 8 GB disk per project |
| Auth users | No limit and no per-user charge | 100,000 MAUs included, then billed per MAU |
| Database backups | Daily backups, 7-day retention. Point-in-Time Recovery included (hourly points, last 7 days) | Daily backups, 7-day retention |
| Static frontend hosting | Free, 1 site per project | Not offered |
| Compute (paid add-on) | From $7 / month (0.5 vCPU shared, 1 GB) | Not offered |
| Best fit | A small product that wants a focused, fixed starting footprint. | A product that needs the wider Supabase platform and more included capacity. |
| Full-stack total | $14 / month | $45 / month Pro $25 + Vercel Pro $20 |
| Point-in-Time Recovery | Included Hourly points, 7 days of coverage | +$100 / month 7 days of coverage |
Comparison is for the stated starting tiers only, not a feature-for-feature comparison. Supabase pricing and included limits were checked on September 26, 2026. See Supabase pricing for current details. Vercel's free Hobby plan prohibits commercial use, so shipped products typically need Vercel Pro.
Or skip the free tier entirely
Hobby vs. Supabase Free.
| KoedoDB Hobby | Supabase Free | |
|---|---|---|
| Full-stack total (DB + Auth + Compute) | $14 / month Hobby $7 + Compute 1 GB $7 | $20 / month Free $0 + Vercel Pro $20 |
| Price | $7 / month | $0 |
| Inactivity pausing | Never pauses | Pauses after 7 days of inactivity |
| Backups | Daily backups, 7-day retention. Point-in-Time Recovery included (hourly points, last 7 days) | Not included |
| Static frontend hosting | Free, 1 site per project | Not offered |
| Compute (paid add-on) | From $7 / month (0.5 vCPU shared, 1 GB) | Not offered |
Supabase Free limits were checked on September 28, 2026. See Supabase project pausing docs for current details. Vercel's free Hobby plan prohibits commercial use, so shipped products typically need Vercel Pro.