SaaS Infrastructure Cost in 2026

The short answer, and why most estimates online are wrong

Founders often want to know what a SaaS costs to run before they know what it costs to build. Fair question. The honest answer is that for most early products the monthly infrastructure bill is small, and the build cost dwarfs it. We cover that side in our SaaS development cost guide. This post is about the bill that arrives every month after launch.

Most articles on this topic quote ranges like "$100 to $250 pre-launch" with no vendor, no date and no assumptions. That isn't useful when you are choosing a stack. So we priced one common setup: Vercel for hosting, Supabase for the Postgres database, file storage and optionally auth, Clerk as the alternative auth provider, Resend or Postmark for email, and Sentry for error monitoring. You could swap any of these for AWS, Render, Auth0 or SendGrid. The shape of the bill stays the same.

All prices are in US dollars, exclude tax, use monthly billing unless the vendor only shows an annual figure, and assume one production project with no overages. Pricing pages change often, so treat the dates as part of the numbers.

Monthly cost by stage

Prototype means you and a handful of testers. First customers means a small paying user base and two developers with access. Growth means tens of thousands of active users, four developers, a bigger database and real backups. The growth column assumes 80,000 monthly active users, which is where the auth decision starts to matter a lot.

What each line actually charges for

Hosting. Vercel Pro is $20 a month and includes $20 of usage credit, and each additional developer seat is another $20. Viewer seats are free. The catch on the free tier is in Vercel's own FAQ: Hobby is for personal, non-commercial use. Once you charge customers, budget for Pro.

Database. Supabase Free gives you 500 MB and two active projects, but free projects pause after a week without activity and have no automatic backups. That is fine for a demo and risky for anything a customer touches. Pro starts at $25, includes $10 of compute credit (enough for the Micro instance), 8 GB of disk and daily backups kept for seven days. Bigger instances cost $15, $60 or $110 a month before the credit. Point-in-time recovery starts at $100 a month, and once real customer data lives in the database we think it is worth it.

Authentication. This is the line founders underestimate. Supabase includes 50,000 monthly active users on Free and 100,000 on Pro, then charges $0.00325 per user. Clerk's free Hobby plan covers 50,000 monthly retained users per app; Pro is $25 a month ($20 billed annually) with 50,000 included, then $0.02 per retained user up to 100,000. At 80,000 retained users that is $25 plus $600. Clerk only counts users who come back 24 hours after signing up, which helps if you get a lot of drive-by signups. Auth0 is free up to 25,000 monthly active users, and its Essentials and Professional plans start at $35 and $240 a month for 500 users, rising with the user count.

Email. Resend's free plan allows 3,000 emails a month but only 100 a day, which a single bulk invite can blow through. Pro is $20 for 50,000 emails, Scale is $90 for 100,000, and extra emails cost $0.90 per thousand. Postmark's free tier is only 100 emails a month; Basic starts at $15 for 10,000.

Storage. Supabase Pro includes 100 GB of file storage, then $0.0213 per GB. Amazon S3 Standard in us-east-1 is $0.023 per GB-month for the first 50 TB, and you pay separately for requests and data transfer out. Cloudflare R2 is $0.015 per GB-month with no egress charges and 10 GB free. For most early products, storage is a rounding error. It only matters if users upload video or large drawings.

Monitoring. Sentry's free Developer plan is limited to one user. Team is $26 a month billed annually with 50,000 errors included and unlimited users. Business is $80. You can also add an uptime monitor here; Sentry includes one on every plan.

Where the bill jumps without warning

Seats grow faster than traffic. Two extra developers on Vercel Pro add $40 a month whether or not a single new customer signs up. Check which tools charge per seat before you invite your whole team, contractors included.

Auth pricing units differ. MAU, MRU and "external active users" are counted differently, and the price per user varies by an order of magnitude between providers. If your product is free to use with a paid upgrade, model auth cost at your target user count before you write the login screen, not after.

Backups are not on by default where you think they are. On Supabase Free there are none, and point-in-time recovery is a paid add-on even on Pro. A restore you have never tested is a hope, not a backup.

Payment fees usually beat infrastructure. Stripe's standard US card rate is 2.9% plus 30 cents per successful charge, with 1.5% more for international cards. On a $29 monthly plan that is about $1.14 per customer per month, before currency conversion. At a few hundred customers, Stripe is likely your largest variable cost, not your servers.

AI features are a separate budget. Model API calls are billed per token and can outgrow everything else on this page quickly. Our AI integration guide covers how to cap that spend.

How we'd keep a young SaaS bill under control

Turn on the spend controls that already exist. Vercel gives new teams a default $200 on-demand budget with alerts and can pause projects at a hard limit. Supabase Pro ships with a spend cap enabled. Leave both on until you understand your usage pattern.

Keep one region and one production project until a customer contract forces otherwise. Preview environments and branch databases are useful, and they are billed too.

Pick auth with your business model in mind. For a B2B product with a few hundred paying seats, Clerk's polish can be worth the per-user price. For a free consumer app aiming at 100,000 users, bundled Supabase Auth changes the economics completely.

Review the invoices monthly for the first six months. Fifteen minutes is enough to catch a forgotten add-on or a seat for someone who left. If you are still choosing between building on a stack like this and buying an existing tool, our custom software vs SaaS guide walks through that decision.

Frequently asked questions

The bottom line

Running a SaaS is cheap until a few specific lines move: seats, auth users, backups and payments. Price those four at the user count you are aiming for, not the one you have today, and the rest of the bill will rarely surprise you.

If you want a second opinion on a stack or an architecture before you commit, look at our SaaS and web development services or read how we approach a custom SaaS build.