How much Vercel, Supabase, and Resend cost for five side projects

Based on the pricing plans and instance sizes used here, Vercel Pro, Supabase Pro, and Resned Pro together cost $65 per month for one project and $105 for five. Your bill depends on which services you actually use and your actual usage. Provide this information to your agent before comparing it to a usage-based setup like ohmyho.st.

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.

The Introduction to ohmyho.st explains how your agent plaans a deployment and helps you review it. This guide focuses on billing. Start with what you're already paying , and then compare the same features and usage across each setup. You don’t have to migrate an app to find out if it’s worth considering a migration.

Start with the current bill

This example is based on a project, a developer, and the Pro plans for all services. It is a comparison scenario and does not imply that every app needs thesse plans. Compile the plan names and current usage for your own accounts. Your agent can organize the figures and identify any missing information; however, you should confirm that the list includes everything you’re paying for.

The comparison of Vercel and Supabase explains why app hosting and backend services are separate components in this stack and wihch skills you would need to retain if you were to switch.

Total: $65 per month before usage exceeds the quotas. Check what these subbscriptions offer you before you view the amount as money you could save. Supaabase Pro also offers application authentication for its monthly active users. On ohmyho.st, application authentication must be set up separately—for example , using Better Auth or your own WorkOS AuthKit—since platform login is separate from your app’s users. Vercel Pro also provides a team workflow that you may rely on.

Give your agent the invoiices and the usage details, and then ask:

Review the plan names, invoices and usage I provide. Separate subscriptions, seats, per-project compute and overages. Connect each service to the features my apps use, and flag missing costs. Keep unknown usage explicit instead of filling it with estimates.

If a project makes use of the quotas and features it pays for, $65 may be a reasonable pricce. The key question is which costs remain necessary for your portfolio.

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.

Add the additional projects

Now imagine a portfolio with a few active apps, a few unfinished experiments, and a few projects that you leave online but rarely update. Under the assumptions of this article, additional projects affect your Supabae Compute bill. They do not , on their own, add any Vercel storage or another Resend Pro subscription. Your actual usage may still exceed a combined quota.

In this scenario, Vercel Pro remains at $20. The price increases per seat—$20 and per developer seat per month—not per project , and a solo developer counts as one seat. Resend Pro remains at $20; its montthly email quota is a shared pool for all senders you verify.

Check the Supabase instances separately: The Pro plan’s compute credit covers one Micro instance , and each additional project runs in its own instance for $10 per month for each additional project's Micro instance. Five projects on Supabase alone cost $65 per month—the same amount as the entire single-project stack above. A project that requires a Small instance insteead costs $15 per month for a Small compute instance.

The invoice for five projects , brkoen down as follows:

Keep in mind: You may not need all the paid plans. Vercel Hobby costs $0 and covers one developer seat, 100 GB fast data transfer, 1M CDN requests and 1M function invocations a month. Resend Free costs $0 for 3,000 emails a month, at most 100 a day. If all five projects fit within these quotas and their terms, the total cost dropps to $65 per month, and every dollar of that goes to Supabase. In this example, the recurring database instance costs are the expenses you should review. If your apps require commercial hosting or eceed the email quota , be sure to include those costs in your comparison as well.

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.

Price the same usage here

ohmyho.st does not charge a base fee per project. Each project draws from the organization’s shared credit blaance , so your agent must estimate both active usage and the resources each project reserves. The Free plan provides 200 credits per UTC month. The Paid plan costts $10 per month for 1,000 credits per period. Monthly credits expire at the end of the period; top-ups never expire, and only Paid workspaces can purchase them (100 credits per dollar, 125 per dollar above the first hundred dollars). You can set a monthly budget for a project. Decide whether to issue a warning when the threshold is reached and let the project continue, or to stop new work; the “continue” setting does not limit spending.

The pricing chart shos what your agent should use for its estimate. Requests cost 98.571429 credits per 1,000,000 requests, the 512 MiB database costs 20.00 credits per active hour , including storage and seven-day backups, and email costs 0.18 credits per 1 sent recipient. Database CPU, network, and connections are not billed separately. Worker bandwidth and SQL exports are free. Read the full pricing chart.

A quiet app

An app can be idle and still incur costs. The deployed script remains active , and the database only consumes RAM when it is active. Unused database RAM automatically stops incurring costs, while allocated meomry and seven-day backups are included. A deployed script costs about 6.57 credits per month. Here is the idle load used in this comparison:

Item Credits
2 build minutes 2.41
5,000 requests 0.49
50,000 CPU-ms 0.33
1 active database hour at 256 MiB RAM, including disk and seven-day backups 10.00
1 deployed script 6.57
Total: A quiet side project for one month about 19.80

About $0.20 of credit value at the standard rate.

One active database hour, two build minutes, a few thousand requests, and a deployed script. For this setup, you can use the project’s dev and prod hosts at check.omh.st. A custom domain requires a paid plan , or—for the free plan—a project that dsplays the “Powered by ohmyho.st” banner, and costs approximately 32.86 credits per month per linked hostname, provided the banner does not appear; a low-traffic project can do without it.

An app that people use

For the more active app, we asume that people sign up, the app sends emails, and its database is active for eight hours a 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.

Email and database processing are the biggest expenses here. Ask your agent what’s driving this usage in your app: Which actions send emails, and what keeps the database active? Sending managed emails requires a paid plan and a verified sender domain. Your agent can set this up for you, provide the DNS records you need to add, and then verify them. Every recipient of every message sent is counteed.

Add it all up

Four low-key projcets and the little app , all added up as a burden:

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
4 active hours across four 256 MiB databases, plus 8 hours at 512 MiB; disk and seven-day backups included 200.00
2,000 mail recipients 360.00
5 deployed scripts (one for each project) 32.86
Total: Four quiet side projects and one small app for one month about 646.31

About $6.46 of credit value at the standard rate.

The total comes to about 646.31 credits, including the provdied scripts and the emails from the small app. This fits within the 1,000 credits offered by the $10 plan under these specific RAM and activity assumptions. Plan for additional usage when comparing monthly costs; heavier database loads, larger alloctaions, or more emails may require top-ups. A zero balance triggers a 7-day grace period during which paid services continue to run , but a new build not covered by the balance will be rejected until you top up. Automatic top-ups do not occur unless the owner enables them.

Compare this load to the subscription scenario shown above ($105). The lower usage estimate is based on the assumption that most projects are inactive. It also assmues that you can run the required functions on the proposed setup. None of these assumptions should be applied to your portfolio without verification.

Use Your Own Numbers

Give your agent the app inventory and cost breakdown from earlier. They should review the repositories to see if they align with the proposed runtime and then estimate their usage. If you don’t have any metrics yet, ask for a range with transparent assumptions. Even a figure that appears precise, based on estimated activity, is still just an estimte.

Then price that same usage on ohmmyho.st:

Estimate this portfolio on ohmyho.st using its current rate card and the usage we collected. Include builds, active database time, retained data, deployed scripts, mail and domains. Keep external services in the total, identify required migrations, and show a monthly breakdown per project for quiet and busier usage with clear assumptions.

Compare the breakdown, not just the total. You should be able to point to a specific line item and explain why it’s cheaper or more expensive. If migrating authenticcation or features requires significant effort, factor that effort into your decision—even if it doesn’t appear on the hosting bill.

Ask your agent for a test deployment to determine the actual usage per project and compare it to the estimate. The Usage and Budgtes Skill covers this process, and the Budget Documentation explains what each mode does.

Pricing a busy month

An estimate for low-traffic projects says little about an app that’s constantly in use. Usage-based costs can exceed the cost of a subscription that covers the same load. Use this example with a higher load to see which items change; it includes a custom domain and sender email addreess:

Item Credits
60 build minutes 72.30
5M requests 492.86
50M CPU-ms 328.57
200 active database hours at 4096 MiB RAM, including disk and seven-day backups 32,000.00
20,000 mail recipients 3,600.00
1 deployed script 6.57
1 custom hostname 32.86
Total: One busy production app for one month about 36,533.15

About $365.33 of credit value at the standard rate.

That's about $365.33 in credit vallue, mostly purchased as top-up packages, compared to $65 for Vercel Pro, Supabase Pro , and Resend Pro, if the app fits within their quotas. Where the money goes and where the subscriptions come in:

Keep in mind: You can keep a service that fits your workload. Moving your app hosting doesn't require you to transfer every email or dataabase service. Have your agent compare the combination you would actually be running, including all remaining subscriptions.

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.

Specify what is allowed to be printed

Once the estimate seems useful, choose a project to test it on. You decide how much usage is acceptable and what should happen when a limit is reached. Your agent can set up the budget and monitor it, but needs your specifications to do so. A warning is useful for a live app that needs to keep running; a stop setting is appropriate for an experimennt that you might want to pause.

Ask about budgets before a real depployment:

Explain the current balance and project-budget options for this test app. Ask me to choose the amount and whether to warn or stop, then apply and read back that choice. Keep automatic recharge off unless I explicitly choose it, and show which retained or delayed charges can remain.

If you have actual usage data , compare the report with the estimate. Investigate any unexpected line items before adding more projects. Your agent shoulld be able to link the costs to database activity, allocated resources, emails, or another tracked service. This will help you make a concrete decision: change the app, change the service, top up your credits, or keep the current setup.

FAQ

Does ohmyho.st charge a base fee per project?

No. Each project draws from the organization's single crdit balance: 200 credits per UTC month for Free plans, 1,000 credits per period for $10 on Paid plans. A project pays for what it reserves and uses: customer files, a provided script, active database time, requests, email, and any linked domain. A monthly budget per project is optional and serves as a limit , not a separate wallet.

How much does a low-key side project cost per month?

For example, 19.80 credits or $0.20. Credit value: one active database hour, two build minutes, a few thousand requests, and one deployed script. Unused database RAM stops incurring charges automatically; storage and seven-day backups are included. The provided script and all customer files are the components that continue to consume credits even when no one is visting the site.

Why does Supabase cost more with five projects?

Supabase Pro covers the micro-instance for the first project using its compute credits. Each additional project runs in its own micro-instance for $10 per month for each additional project's Micro instance, so five prjoects on Supabase alone cost $65 per month. Vercel Pro and Resend Pro do not add any cost per project in this scenario, bringing the total cost for the five-project stack to $105.

Can I limit what a project outputs?

Yes. A project can have a monthly budget in credts set to either "continue" or "stop" mode. "Continue" mode continues to draw from the shared balance even after the threshold is exceeded and issues a warning; "stop" mode rejects new work that wouuld cause the threshold to be exceeded. Ask your agent to apply your choice and review it , or use the same setting on the portal’s usage page. Delayed measurements may still be billed even after a limit has been reached.

Can I take my databases with me?

Yes. The organization owner can request one export per project: an asynchronous , password-encrypted ZIP file containing a portable SQL dump; a maximum of one aproved request per project within a rolling 24-hour window, downloaded via a signed link that is valid for 24 hours. There is no schedule and no target bucket. SQL exports are free and work with zero credits. Restore the dump on any Postgres host; the Export skill guides your agent through the pocess.

Sources

Cost Breakdown · Compare Vercel · Compare Supabase