# What Vercel, Supabase and Resend cost for five side projects By Sebastian Mertens · September 20, 2026 One project on Vercel Pro, Supabase Pro and Resend Pro costs $65 a month. Five projects cost $105, because Supabase adds $10 a month for each extra project. On ohmyho.st the same five draw from one balance: $10 a month buys 1,000 credits, and four quiet projects plus one small app use about 829.54 credits.
List prices checked on September 19, 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.
## One project, bought separately Start with the honest baseline: one project, one developer, the three Pro plans most tutorials assume. Three accounts, three invoices, three usage pages to check at the end of the month. - Vercel Pro: $20 per month for one developer. It comes with $20 of usage credit each month and free viewer seats. A second person who deploys is another $20 per developer seat per month. Function invocations above the credit cost $0.60 per million. - Supabase Pro: from $25 per month. That covers 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. Disk above that is $0.125 per GB of disk per month beyond 8 GB per project. - Resend Pro: $20 per month for 50,000 emails a month; pay-as-you-go overage is opt-in. Beyond that, $0.90 per 1,000 emails beyond the plan when pay-as-you-go is enabled. Total: $65 a month before any usage above the allowances. Be fair to that number. It buys more than hosting, a database and mail. Supabase Pro carries application auth for its monthly active users, which ohmyho.st does not run for you; you bring Better Auth or your own WorkOS AuthKit, and the platform login stays separate from your app's users. Vercel Pro carries a team workflow a solo builder may never touch. If one project is all you run and it fills those allowances, $65 is a reasonable price for it. 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). ## Five projects The portfolio builder's problem is never one project. It is five: two that people use, one that is half done, two that are finished and just sit there. Price the same three subscriptions for five projects and only one vendor moves. Vercel Pro stays at $20 in this scenario. Its price grows by seat, at $20 per developer seat per month, not by project, and a solo builder has one seat. Resend Pro stays at $20; its monthly email allowance is one pool shared by every sender you verify. Supabase is the one that counts projects. Its own math is simple: Pro's compute credit covers one Micro instance, and each additional project runs its own at $10 per month for each additional project's Micro instance. Five projects on Supabase alone are $65 a month, the same figure as the whole one-project stack above. A project that needs a Small instance instead is $15 per month for a Small compute instance. The five-project bill, itemized: - Vercel Pro: $20 - Supabase Pro, first project: $25 - Four more Supabase Micro projects: $10 each - Resend Pro: $20 - Total: $105 a month The free tiers, honestly. Vercel Hobby is $0 and covers one developer seat, 100 GB fast data transfer, 1M edge requests and 1M function invocations a month. Resend Free is $0 for 3,000 emails a month, at most 100 a day. If all five projects fit inside those allowances and their terms, the stack drops to $65 a month, and every dollar of it goes to Supabase. That is the point of this post: for a portfolio, the per-project fee is the bill, not the hosting. 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). ## The same five on ohmyho.st There is no per-project base fee. Every project draws from the organization's one balance. Free gives 200 credits per UTC month. Paid is $10 a month for 1,000 credits per period; monthly credits expire at the end of the period, and a top-up pack never expires (100 credits per dollar, 125 per dollar above the first hundred dollars). A project may carry a monthly budget, continue or stop, so one experiment cannot drain the other four. Credits are priced from what the providers underneath charge, plus a margin, and the rate card is public. The rates that decide a side project's month: requests at 98.571429 credits per 1,000,000 requests, database compute at about 36.47 credits per active hour on the Paid standard profile, storage at 115 credits per 1 GB-month, mail at 52.571429 credits per 1,000 recipients. Bandwidth from the Workers runtime is not charged. SQL exports are free. The full card is at [docs.ohmyho.st/pricing](https://docs.ohmyho.st/pricing). ### A quiet project A finished side project keeps paying for three things: the data it stores, the script that serves it, and the minutes its database is awake. Idle database compute suspends on its own. A deployed script is about 6.57 credits a month. Here is a quiet month, line by line: | Item | Credits | | --- | ---: | | 2 build minutes | 2.41 | | 5,000 requests | 0.49 | | 50,000 CPU-ms | 0.33 | | 1 active database hour on the Paid standard 0.5 CU profile | 36.47 | | 0.2 database GB-month | 23.00 | | 1 deployed script | 6.57 | | **Total: A quiet side project for one month** | **about 69.27** | About $0.69 of credit value at the standard rate. One active database hour, two build minutes, a few thousand requests, a fifth of a gigabyte stored. The project stays on its Dev and Prod hosts under check.omh.st. A customer-owned domain is a Paid capability that uses credits, about 32.86 credits a month per linked hostname; a quiet project can skip it. ### The small app One of the five is real. People log in, it sends mail, and its database 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 | | 4 database CU-hours (8 active hours on the Paid standard 0.5 CU profile) | 291.77 | | 1 database GB-month | 115.00 | | 2,000 mail recipients | 105.14 | | **Total: A small app for one month** | **about 552.44** | About $5.52 of credit value at the standard rate. The database line dominates, and it is the one you control: fewer active hours, fewer credits. Sending mail needs Paid and a verified sender subdomain; the agent sets DKIM and SPF through mail_domain_set and reads mail_domain_status until the records verify. Every recipient is metered, and To, CC and BCC count separately. ### Five together Four quiet projects and the small app, added up as one workload: | Item | Credits | | --- | ---: | | 28 build minutes (2 for each quiet project, 20 for the small app) | 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 | | 2,000 mail recipients | 105.14 | | 4 deployed scripts (one for each quiet project) | 26.29 | | **Total: Four quiet side projects and one small app for one month** | **about 829.54** | About $8.30 of credit value at the standard rate. About 829.54 credits, inside the 1,000 credits that $10 buys, with room for a few extra builds. Two lines are missing, because the small-app workload leaves them out: the small app's own deployed script, and the mail sender zone behind its verified subdomain, about 164.29 credits a month. Count both and the five projects use about 1,000.40 credits: the monthly grant and a fraction of a credit more. Keep one top-up pack in the balance. A zero balance starts a seven-day grace period during which funded services keep running, but a new build the balance cannot cover is rejected until you refill. Automatic recharge is not enabled yet. Set that against the $105 a month from the section above. The difference is not a discount. It is that four of the five projects are quiet, and here quiet costs almost nothing. ### How to price your own five Paste this into Claude Code, Cursor or Codex from the repository you want to host first: ```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. ``` The agent reads the get-started Skill, signs you in through the browser, creates the project with project_create, links the repository with source_link and quotes the build with deployment_plan before deployment_create runs. Every plan states its credits before anything is charged. Once two or three projects are live, ask the agent for a cost report: it calls organization_usage_get and organization_credits_get and tells you which project used what. If one experiment must never spend more than a set amount, project_budget_set gives it a ceiling with continue or stop. The [usage and budgets Skill](/skills/ohmyhost-usage-and-budgets/SKILL.md) describes the whole loop, and [budgets](https://docs.ohmyho.st/budgets) has the exact semantics. ## What changes at scale Metering cuts both ways. A quiet project costs less than any subscription; a busy one can cost more. Here is one busy production app with its own domain and sender mail: | Item | Credits | | --- | ---: | | 60 build minutes | 72.30 | | 5M requests | 492.86 | | 50M CPU-ms | 328.57 | | 100 database CU-hours (200 active hours on the Paid standard profile) | 7,294.29 | | 10 database GB-months | 1,150.00 | | 20,000 mail recipients | 1,051.43 | | 1 deployed script | 6.57 | | 1 custom hostname | 32.86 | | 1 mail sender zone | 164.29 | | **Total: One busy production app for one month** | **about 10,593.15** | About $105.93 of credit value at the standard rate. That is about $105.93 of credit value, most of it bought as top-up packs, against $65 for Vercel Pro, Supabase Pro and Resend Pro, if the app fits inside their allowances. Where the money goes, and where the subscriptions win: - The database. Two hundred active hours on the standard profile cost about 7,294.29 credits. Supabase Pro runs a Micro instance all month inside its $25, and a Small instance is $15 per month for a Small compute instance. An app whose database never sleeps belongs on a fixed instance. The performance profile on ohmyho.st is about 91.18 credits per active hour and gives more compute, not a lower bill. - Mail. Twenty thousand recipients cost about 1,051.43 credits. Resend Pro's $20 covers 50,000 emails a month; pay-as-you-go overage is opt-in. Use that whole allowance and Resend wins: 50,000 mail recipients in one month costs about 2,628.57 credits here. - Requests. Neither bill is decided here. The busy app's requests line is small, and Vercel Pro bills $0.60 per million function invocations above its credit. - Team and auth. Vercel Pro's viewer seats are free. Supabase Pro authenticates its monthly active users for you. ohmyho.st runs neither: application auth stays with Better Auth or your own WorkOS AuthKit, and every extra collaborator needs nothing from the balance because there are no seats to buy. - Previews and runtimes. Every ohmyho.st project has a Dev host and a Prod host, not a preview per branch. It deploys Next.js, Vite/React and TanStack Start from a GitHub repository you authorize, and nothing else; no containers. Rule of thumb: many quiet projects, meter them. One busy project with an always-awake database, buy the instance. 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). ## FAQ ### Does ohmyho.st charge a base fee per project? No. Every project draws from the organization's one balance: 200 credits a UTC month on Free, 1,000 credits per period for $10 on Paid. A project pays for what it keeps and uses: stored data, a deployed script, active database time, requests, mail and any linked domain. A monthly budget per project is optional and is a limit, not a second wallet. ### What does a quiet side project cost a month? About 69.27 credits, or $0.69 of credit value: one active database hour, two build minutes, a few thousand requests, a fifth of a gigabyte stored and one deployed script. Idle database compute suspends by itself. Storage and the deployed script are the parts that keep using credits while nobody visits. ### Why does Supabase cost more with five projects? Supabase Pro covers the first project's Micro instance through its compute credits. Each additional project runs its own Micro instance at $10 per month for each additional project's Micro instance, so five projects are $65 a month on Supabase alone. Vercel Pro and Resend Pro add no per-project line in this scenario, which puts the whole five-project stack at $105. ### Can I cap what one project spends? Yes. A project may carry a monthly budget in credits with mode continue or stop. Continue keeps drawing from the shared balance past the threshold and warns; stop rejects new work that would exceed it. The agent sets it with project_budget_set and reads it back with project_budget_get, and the portal's usage page edits the same setting. Delayed measurements can still settle after a limit is reached. ### Can I take my databases with me? Yes. The organization Owner can request an export per project: an asynchronous, password-encrypted ZIP with a portable SQL dump, at most one accepted request per project per rolling 24 hours, downloaded through a signed link valid for 24 hours. There is no schedule and no bucket destination. SQL exports are free and work at zero credits. Restore the dump on any Postgres host; the [export Skill](/skills/ohmyhost-export-database/SKILL.md) walks the agent through it. ## 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). [Cost breakdown](/pricing/breakdown) · [Compare Vercel](/vs/vercel) · [Compare Supabase](/vs/supabase)