# Supabase vs Vercel: do you need both?

By Sebastian Mertens · September 20, 2026

For most small apps, yes: Vercel Pro is $20 a month and Supabase Pro starts at $25, because neither one does the other's half. ohmyho.st puts hosting and Postgres on one balance: $10 a month buys 1,000 credits shared by every project, and a quiet side project uses about 69.27 credits.

<figure class="fig" aria-label="Vercel Pro, Supabase Pro and Resend Pro for one developer and one project: $65 a month, against one ohmyho.st balance from $10 a month."><figcaption>List prices checked on September 19, 2026 · <a href="https://vercel.com/pricing" rel="noopener">Vercel pricing</a> · <a href="https://supabase.com/pricing" rel="noopener">Supabase pricing</a> · <a href="https://resend.com/pricing" rel="noopener">Resend pricing</a>. ohmyho.st: $10 a month buys 1,000 credits shared by every project; hosting, Postgres, mail and a linked domain are metered from that balance.</figcaption></figure>

## What Vercel does and what it charges

Vercel takes a Git repository, builds the frontend, serves the static files from its CDN and runs the server code as functions. It is very good at that. It does not run a Postgres database of its own; databases on Vercel come through marketplace partners or a separate account, which is where Supabase enters the picture.

Hobby costs $0 and comes with one developer seat, 100 GB fast data transfer, 1M edge requests and 1M function invocations a month. Vercel's own FAQ says Hobby is for personal, non-commercial use (vercel.com/pricing, read 2026-09-20). A client site or an app that takes payments belongs on Pro.

Pro costs $20 per month. That fee comes back as usage credit each month, so the first $20 of function and build usage costs nothing extra; CDN requests and fast data transfer carry no overages on Pro, and viewer seats are free. Each further developer is $20 per developer seat per month. Function invocations beyond the credit are $0.60 per 1M function invocations beyond the included credit.

The shape matters more than the number. Vercel bills per seat, not per project, so one developer with nine side projects pays the seat once. That is the good news for a portfolio builder. The bad news is that the seat is due whether the nine projects had a million visitors or none.

List prices checked on 2026-09-19 — [Vercel pricing](https://vercel.com/pricing).

## What Supabase does and what it charges

Supabase is a Postgres database with a REST API, Auth, Storage, Realtime and Edge Functions wrapped around it, plus a table editor in the browser. It does not host your Next.js app. It hosts the data and the services your app calls.

The Free plan is where most portfolios start, and it has two rules that bite: Supabase pauses a Free project after a short stretch of inactivity, and it limits how many Free projects can be active at once (supabase.com/pricing, read 2026-09-20). A paused project does not answer until you restore it from the dashboard. For a side project that gets a visitor every few weeks, that is a broken link most of the time.

Pro starts at $25 a month and includes the first project's Micro instance through $10 of compute credits, 8 GB disk per project, 250 GB egress a month, 100,000 monthly active users. The catch is in the word "first": every further project runs its own compute instance at $10 per month for each additional project's Micro instance, and a Small instance is $15 per month for a Small compute instance. Disk beyond the allowance is $0.125 per GB of disk per month beyond 8 GB per project; egress beyond the allowance is $0.09 per GB of egress per month beyond 250 GB.

So Supabase bills per project, the opposite of Vercel. The instance runs around the clock and the charge is the same at zero queries and at a thousand. That is fine for one product. It is expensive for a shelf of experiments.

List prices checked on 2026-09-19 — [Supabase pricing](https://supabase.com/pricing).

## Why most small apps end up with both

Vercel hosts, Supabase stores. A Next.js app with a login form and a table of records needs both halves, so the default stack for a vibe-coded app is Vercel for the app, Supabase for Postgres and Auth, and a third account for transactional mail. The figure above adds Resend Pro for that reason. Three accounts, three dashboards, three invoices, three places where a card can expire.

Nothing is wrong with either product. The problem is how the two pricing shapes combine for one person with several small apps:

- Vercel charges per seat, so the project count does not move the bill.
- Supabase charges per project, so every extra app is another $10 a month on Pro, or a Free project that pauses.
- Neither bill falls when a project goes quiet. Capacity is reserved; usage is not what you pay for.

The portfolio builder's fifth app has a dozen users and a database that wakes up twice a day. On this stack it costs the same as the first app did.

List prices checked on 2026-09-19 — [Supabase pricing](https://supabase.com/pricing).

## When one balance replaces both

ohmyho.st is hosting for vibe-coded apps. Your coding agent deploys a Next.js, Vite/React or TanStack Start repository from GitHub through MCP tools (`deployment_plan`, then `deployment_create` once you confirm), and every project gets managed Postgres, a Dev host and a Prod host on a three-words.check.omh.st address and, on Paid, a custom domain and sender mail, both of which use credits. All of it is metered from one organization balance. There is no per-project base fee and no deploy dashboard; the portal at app.ohmyho.st shows projects, credits, budgets and API tokens.

The plans are short. Free grants 200 credits per UTC month. Paid is $10 a month for 1,000 credits per period; those expire at period end, while top-ups at 100 credits per dollar never expire. One credit is $0.01 of credit value.

The rates a small app meets: 98.571429 credits per 1,000,000 requests; 72.942857 credits per 1 CU-hour, so one active hour on the Paid standard 0.5 CU profile is about 36.47 credits; stored data is 115 credits per 1 GB-month; each deployed script is about 6.57 credits a month. Bandwidth from Workers is not charged. Database compute suspends after a minute idle, so a project nobody visits pays for its stored data and its script, nothing else. That is the property a Supabase Micro instance does not have.

Now the math. Bought separately, one project on Vercel Pro and Supabase Pro is $45 a month before usage; with Resend Pro for mail it is the $65 in the figure. Five projects on the same Vercel and Supabase accounts are $85 a month, because four extra Micro instances run around the clock.

On ohmyho.st, five side projects, one of them with real traffic and login mail, look like this:

| Item | Credits |
| --- | ---: |
| 28 build minutes | 33.74 |
| 120,000 requests | 11.83 |
| 1.2M CPU-ms | 7.89 |
| 6 database CU-hours (12 active hours on the Paid standard 0.5 CU profile across five databases) | 437.66 |
| 1.8 database GB-months | 207.00 |
| 500 mail recipients | 26.29 |
| 1 mail sender zone (one project sends mail) | 164.29 |
| 5 deployed scripts | 32.86 |
| **Total: A portfolio of five side projects for one month** | **about 921.54** |

About $9.22 of credit value at the standard rate.

That fits inside the 1,000 credits the Paid plan grants each period. The fixed part is stored data, five scripts and one mail sender zone; everything else only accrues while someone uses an app. On its own, the small app is about 552.44 credits and each quiet side project about 69.27 credits. The headroom is real but not huge. If one app gets popular, give it a monthly budget through `project_budget_set` (continue or stop) so it cannot drain the others, and buy a top-up when the balance runs low. A zero balance starts a 7-day grace period; funded services keep running, and only unfunded services suspend afterwards.

To try it, open your repository in Claude Code and paste this:

```text
Read https://ohmyho.st/llms.txt and https://ohmyho.st/skills/ohmyhost-get-started/SKILL.md. Connect this agent to ohmyho.st and deploy this GitHub project using only the capabilities it needs. Follow the deployment Skill, keep my existing project decisions and verify the app.
```

List prices checked on 2026-09-19 — [Vercel pricing](https://vercel.com/pricing).
List prices checked on 2026-09-19 — [Supabase pricing](https://supabase.com/pricing).
List prices checked on 2026-09-19 — [Resend pricing](https://resend.com/pricing).

## When it does not

Be honest about the other direction.

**You use Supabase for more than Postgres.** Auth, Realtime, Storage and Edge Functions are real products, and a SQL dump moves none of them. ohmyho.st does not replace your auth provider; Better Auth and customer-owned WorkOS AuthKit are the verified integrations, and Realtime subscriptions or Edge Functions may have no direct equivalent in the runtime. The [migration Skill](/skills/ohmyhost-migrate-supabase-postgres/SKILL.md) inventories what the app actually calls, converts only what you select and states a gap instead of faking a success. If those services are the app, stay.

**You have one busy app, not many quiet ones.** A single busy production app with millions of requests, hundreds of active database hours, a linked domain and sender mail is about 10,593.15 credits a month, roughly $105.93 of credit value bought as top-ups. Vercel Pro and Supabase Pro at $45 may well come out cheaper there, before their overages. Metering favors the quiet portfolio; reserved capacity favors the steady product.

**You want previews and a dashboard.** Vercel builds a preview for every branch and lets viewers in for free. ohmyho.st gives each project a Dev host and a Prod host, promotes Dev to Prod through `promotion_plan` and `promotion_execute`, and has no per-branch previews. Deploys go through the agent, not through a web UI.

**Your framework is not on the list.** Supported today: Next.js, Vite/React and TanStack Start, deployed from a GitHub repository you authorize. No containers, no other deployment source. SvelteKit, Nuxt, Astro or a Dockerfile do not run here yet; Vercel runs most of them.

**Everything fits the free tiers.** A personal project with steady traffic on Vercel Hobby at $0 plus a Supabase Free project that never pauses costs nothing, and no balance beats nothing. The case for one balance starts when the pauses, the non-commercial rule or the per-project instances start to hurt.

List prices checked on 2026-09-19 — [Vercel pricing](https://vercel.com/pricing).
List prices checked on 2026-09-19 — [Supabase pricing](https://supabase.com/pricing).

## FAQ

### Do I need both Supabase and Vercel?

If you stay with them, yes. Vercel hosts the app and leaves the database to a partner or another account; Supabase hosts the database and does not serve a Next.js app. A database-backed app therefore needs both accounts. The alternative is a host that meters hosting and Postgres from one balance, which is what ohmyho.st does: no per-project base fee, one pool of credits shared by every project.

### Can I keep Supabase and move only the hosting?

Yes. The migration Skill inventories what the app really uses and converts only the capabilities you select; the rest stays external. An app that talks to Supabase over its HTTPS API keeps doing so once the agent lists that origin in the app's egress rules, and you keep paying Supabase for it. Move the database later, or never.

### What happens to my Supabase Auth users?

They do not travel inside a SQL dump. ohmyho.st does not replace your auth provider: Better Auth and customer-owned WorkOS AuthKit are the verified integrations, and the platform login is separate from your application's users. The migration Skill asks you to decide before touching Auth, then tests login, a protected route, reload and logout on the Dev host before anything is promoted.

### What does a quiet side project cost on ohmyho.st?

About 69.27 credits a month, or about $0.69 of credit value: one active database hour, a little stored data, a few thousand requests and one deployed script. Idle database compute suspends after a minute; stored data at 115 credits per 1 GB-month and the script keep using credits while the project exists.

### Can I take my database with me later?

Yes. An Owner asks the agent for an export through `project_export_create`: an asynchronous, password-encrypted ZIP holding a portable SQL dump, one accepted request per project in any rolling 24-hour window, downloaded through a signed link that stays valid for 24 hours. Exports are free and work at zero credits. Restore the dump on any Postgres host, including Supabase.

## Sources

- List prices checked on 2026-09-19 — [Vercel pricing](https://vercel.com/pricing).
- List prices checked on 2026-09-19 — [Supabase pricing](https://supabase.com/pricing).
- List prices checked on 2026-09-19 — [Resend pricing](https://resend.com/pricing).

[Compare Supabase](/vs/supabase) · [Compare Vercel](/vs/vercel) · [From Vercel and Supabase](/from/vercel-supabase)