Vercel alternative with a database: ohmyho.st vs Vercel

You ship the app on Vercel, the database on Supabase and the mail on Resend. That is three dashboards, three invoices and three usage models to keep in your head — and the two side projects nobody visited this month cost you exactly as much as the one that did.

ohmyho.st puts those four pieces on one prepaid balance. $10 a month buys 1,000 credits, every project you run draws from the same balance, and a quiet project spends almost nothing. Vercel Pro alone is $20 a month before you have a database or a way to send a password-reset mail; the usual three-subscription stack is $65 a month. A small app here uses about 567.10 credits a month.

vercel pro$20 /mosupabase pro, 1 project$25 /moresend pro$20 /mo$65 /mo3 accounts · 1 project · +$10 each extra projectohmyho.st · every projecthostinguses creditspostgresuses creditsemailuses creditslink a domainuses creditseach extra projectno base fee$10 /mo1 balance · 1,000 credits a month
List prices checked on September 28, 2026 · Vercel pricing · Supabase pricing · Resend pricing. 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.

What Vercel charges

Vercel sells the front end and its functions, and charges for every person who deploys. It does not run your Postgres and it does not send your mail. That is where the second and third subscription come from — not from Vercel being expensive, but from Vercel being one part of what an app needs.

The database and the mail are where the bill grows. Supabase Pro starts at $25 a month and covers the first project's Micro instance through its compute credits; every further project's Micro instance adds $10 a month. Resend Free is $0 with 3,000 emails a month, at most 100 a day. Resend Pro is $20 per month with 50,000 emails a month; pay-as-you-go overage is opt-in.

One developer with one project on all three accounts: $65 a month before any usage above the allowances. The same accounts with five projects: $105 a month, because every extra Supabase project pays its own instance while Vercel Pro and Resend Pro stay the same.

List prices checked on 2026-09-28 — Vercel pricing. List prices checked on 2026-09-28 — Supabase pricing. List prices checked on 2026-09-28 — Resend pricing.

What ohmyho.st charges for the same small app

One balance, every project, no seat price. $10 a month buys 1,000 monthly credits that expire at billing-period end without rollover. Free gets 200 credits per UTC month. Paid-only top-ups carry over until downgrade to Free: 100 credits per dollar, and 125 per dollar on the part of a larger purchase. A credit has a nominal value of $0.01. There is no per-project base fee and no seat price: an organization has one balance, every project draws from it, and a second person who deploys costs nothing extra.

This is hosting for vibe-coded apps priced by what the app measures. Here is the workload the rate card prices for a small app with some traffic, some mail and a database that is awake for eight hours across the month:

Item Credits
20 build minutes 24.10
100,000 requests 9.86
1M CPU-ms 6.57
8 active database hours at 512 MiB RAM, including disk and seven-day backups 160.00
2,000 mail recipients 360.00
1 deployed script 6.57
Total: A small app for one month about 567.10

About $5.67 of credit value at the standard rate.

Read the table from the largest line down. Mail and the database account for much of this example. One active database hour at 512 MiB RAM costs 20.00 credits; the 256 MiB size available on Free costs 10.00 credits. Databases sleep after five idle minutes, with no active-RAM charge while asleep. Allocated disk and seven-day backups are included. Customer files and retained Worker scripts keep their separate rates. Requests use 98.571429 credits per 1,000,000 requests; Worker bandwidth is not charged. Mail is 0.18 credits per 1 sent recipient, counted per sent recipient, and needs Paid plus a verified mail domain.

Two things keep drawing credits while a project sits still: each deployed script, about 6.57 credits a month, and a linked custom hostname, about 32.86 credits a month, nothing while the project shows the “Powered by ohmyho.st” flag. A mail domain has no monthly fee. SQL exports are free. A quiet side project whose database wakes for one hour a month costs about 19.80 credits. Five of them cost about 99.01 credits, which leaves most of the monthly 1,000 unused.

Side by side

Bought separately

Vercel Pro, Supabase Pro and Resend Pro for one developer and one project

Vercel Pro$20
Supabase Pro, 1 project$25
Resend Pro$20
Each extra project+$10
3 accounts, 1 project$65/mo

List prices checked on September 28, 2026: Vercel, Supabase, Resend.

ohmyho.st

one balance, every project

Hostinguses credits
Postgresuses credits
Emailuses credits
Link a domainuses credits
Each extra projectno base fee
1 balance, every project$10/mo

$10 a month buys 1,000 credits. A small app for one month costs about 567.10 credits; a quiet project keeps only its deployed script and any customer files.

The left card is one developer and one project. It costs $65 before any usage above the allowances and before a second developer seat. Add four more projects to the same accounts and the left card becomes $105, because each Supabase project after the first pays $10 a month. The right card stays at $10 whether you run one project or nine; what changes is how fast the 1,000 credits go. The small app above uses about 567.10 credits of them, $5.67 of credit value.

The trade-off is metering with no quota to hide behind. One busy production app, with a database awake for 200 hours a month, 5M requests and 20,000 mail recipients, uses about 36,533.15 credits: $365.33 of credit value against $65 for the three subscriptions. Many quiet projects favor ohmyho.st; one loud one favors Vercel and Supabase.

List prices checked on 2026-09-28 — Vercel pricing. List prices checked on 2026-09-28 — Supabase pricing. List prices checked on 2026-09-28 — Resend pricing.

When Vercel is the better choice

List prices checked on 2026-09-28 — Vercel pricing. List prices checked on 2026-09-28 — Supabase pricing.

When ohmyho.st is

How to move with your agent

Hosting moves first; the database moves only if you want it to. If your app uses Supabase purely as Postgres, the migration Skill converts the queries to the managed database binding, keeps the versioned migrations and verifies reads and writes on Dev. If it uses Supabase Auth, Storage, Realtime or Edge Functions, keep Supabase as an external service and point the hosted app at it: a database dump does not migrate those services, and the Skill says which capability stays external before it changes anything. Resend can stay the same way until you want mail metered here.

Keep the existing project's current source, or choose managed versions or an authorized GitHub repository for a new app. Push changes when GitHub is selected; managed source saves the filtered current files. Then paste this prompt into your available coding agent with the selected app open:

Read https://ohmyho.st/llms.txt and https://ohmyho.st/skills/ohmyhost-get-started/SKILL.md. Connect this agent to ohmyho.st and develop and deploy this application using only the capabilities it needs. Read the existing project source first and follow the get-started Skill to reuse GitHub or managed versions for this workspace. After signing in, use the user and organization that whoami reports; never guess an account, organization or project ID. Follow the deployment Skill, keep my existing project decisions and verify the app.

What happens next, step by step:

  1. The agent checks what is installed and signed in. If nothing is, it sends you one browser link with a confirmation code; you sign in once and it verifies the session with a command.
  2. It reads the project/source binding first and inspects the available app files. For a local checkout it runs ohmyhost init --dry-run; GitHub is connected through github_connect only when selected and needed. Managed source saves an exact current-file version instead.
  3. It reuses the existing project or calls project_create when you request a new one, choosing US or EU once. Data mode is optional and defaults to shared; isolated data keeps Dev and Prod separate, and an Owner can change the assignment later through a confirmed plan without copying data. It then asks for a deployment_plan. You read the plan, including the build cost it reserves, and confirm; deployment_create builds the commit. Secrets use the local stdin command from secret_set_command or the supported remote private portal input, never pasted into chat or source.
  4. Dev is protected by default. project_dev_share_link_get gives you a reusable share link; test login, a protected route and a real read and write. Then promotion_plan and promotion_execute publish to Prod at your project's three-word host on check.omh.st without a rebuild.
  5. After Prod works, domain_paid_plan then domain_paid_apply link your own hostname on Paid, or on Free while the project shows the “Powered by ohmyho.st” flag; the flag waives domain credits on either plan. Managed mail needs Paid: mail_setup then mail_status set up the sender domain, return its DNS records and wait for verification. Move your DNS when Prod works, then cancel the Vercel Pro seat.

FAQ

Is ohmyho.st cheaper than Vercel?

For a portfolio of small apps, usually. $10 a month buys 1,000 credits shared by every project, and the small app above uses about 567.10 credits of them. Vercel Pro is priced per developer seat and still needs a database and a mail provider beside it. One busy app whose database is awake all day can cost more here, so read the busy workload before deciding.

Can I keep Supabase and only move the hosting?

Yes. The migration Skill converts only the capabilities you pick. If the app uses Supabase Auth, Storage, Realtime or Edge Functions, keep Supabase as an external service and point the hosted app at it. If it uses Supabase only as Postgres, the agent can move the schema and the rows to the managed database and verify reads and writes on Dev before Prod.

Is there a free plan?

Yes. Free gives 200 credits per UTC month, a Dev and a Prod host on check.omh.st and a database on the 256 MiB RAM size with 500 MiB disk and seven-day backups included at the same rates as Paid. Sending mail needs Paid at $10 a month. A custom domain needs Paid as well, or on Free a project that shows the small “Powered by ohmyho.st” flag; the flag also waives domain credits. Monthly credits expire at the end of their Free month or Paid billing period. Top-ups carry over while Paid and expire on downgrade to Free.

How do I get my database out?

Ask the agent for project_export_create. You get a password-encrypted ZIP with a portable SQL dump, at most one accepted request per project per rolling 24 hours, through a signed link valid for 24 hours. Exports are free and still work at zero credits. Restore the dump on any Postgres host; files and source are not part of it.

Do I need a coding agent to use it?

Yes. There is no deploy dashboard. Deployments, promotions, domains, mail and exports run through the 114 MCP tools from Claude Code, Cursor or Codex, or through the CLI. The portal at app.ohmyho.st shows projects, credits, budgets and API tokens; it does not deploy anything.

What happens when my credits run out?

A zero balance starts a 7-day grace period during which funded services keep running. After it, only unfunded services suspend; your data, an export and buying credit stay available. A project can carry a monthly budget set to continue or stop. Automatic recharge stays off unless the Owner turns it on, so nothing charges your card on its own.

Sources

Cost breakdown · From Vercel and Supabase · vs Supabase · What Vercel, Supabase and Resend cost for five side projects · Free Vercel and Supabase alternatives · Vercel and Supabase in one platform

ohmyho.st is an independent service, not affiliated with or endorsed by Vercel, Supabase or Resend. All trademarks belong to their respective owners.