SaaS maintenance cost / 2026 numbers

What it actually costs to keep a SaaS app alive.

Most answers to this question are written by agencies quoting percentages of a development budget you may never have had. This one is written for the owner of a small app, very possibly one an AI helped build, who needs real monthly numbers and an honest map of who charges what. Including where paying nothing is the right call.

monthly bill · small revenue app, 2026
hosting (vercel pro)$20
database (supabase pro)$25
email + third-party apis$35
error tracking + uptime$10
domain, misc$5
a human who watches + fixes$300-1,500
the infrastructure is cheap. the question is the last line.

The short answer

As of July 2026, a small SaaS app costs about $20 to $100 a month in infrastructure. A hobby project runs nearly free. A side project with real users lands around $100 to $400 a month all-in. A revenue business with nobody technical on staff should budget $500 to $2,000 a month.

The industry's favorite formula, 15 to 20 percent of your development cost per year, was invented for software that cost six figures to build. If your app cost $100,000, it predicts $15,000 to $20,000 a year of upkeep, and it is roughly right. If an AI built your app for a few hundred dollars in subscriptions, it predicts $5 a month, and it is uselessly wrong. The rest of this page budgets from the actual cost drivers instead.

Where the money goes

Seven things you are actually paying for.

Maintenance is not one bill, it is seven overlapping jobs. The first three are cheap and mostly automated. The last four are where skilled humans enter the picture, and where the real budget decisions live.

C1
Hosting and infrastructure
The predictable line. Vercel, Netlify, Railway, or similar at $0 to $20/mo for small apps, plus a managed database like Supabase or Neon at $0 to $25/mo. Scales with traffic, but slowly. Free tiers genuinely cover hobby use.
C2
Third-party APIs
Email, SMS, maps, payments, and above all AI APIs. Usually $15 to $50/mo for a small app, but this is where surprise bills live: an unguarded LLM endpoint or a retry loop can turn $30 into $800 in a weekend.
C3
Monitoring and alerting
Uptime checks, error tracking, log retention. Free to $30/mo in tools. The real cost is the human who reads the alerts, because an unread alert is the same as no alert.
C4
Security patching
Closing holes when they are found: in your code, your dependencies, or your configuration. Irregular but non-optional if you hold user data. This is skilled work, priced per fix or bundled in a care plan.
C5
Dependency updates
Frameworks, libraries, and platform SDKs move constantly. Skipping updates feels free until a security release forces you to jump twelve versions at once. Steady small updates are dramatically cheaper than one giant one.
C6
Incident response
When the app goes down or something breaks in production, someone has to be findable, able to read the system, and calm. This is the most expensive capability to buy on demand and the cheapest to buy as a standing arrangement.
C7
Feature drift
The world moves: an API you depend on deprecates, a browser change breaks your layout, users need one small thing changed. Not quite new development, not quite repair. Most owners underestimate how much of maintenance is this.

Notice the pattern: the tooling is cheap and getting cheaper, while the judgment is not. An uptime monitor costs nothing. Knowing whether the 3am alert is cosmetic or existential, and being the person who fixes it either way, is the part that has a price.

Budget bands

What to budget, by what your app actually is.

Forget percentage rules. The honest budget follows two questions: does the app have something to lose, and is anyone technical already on your side? Three profiles cover most owners reading this.

Hobby app
No revenue, no sensitive data, downtime is a shrug
$0 to $30/mo

Free hosting tiers, free monitoring, DIY everything. Paying for maintenance here is premature. Your only real obligations: keep the domain renewed on your own card and take an occasional database backup.

Side project with real users
Some users, maybe early revenue, reputation at stake
$100 to $400/mo

Paid infrastructure tiers ($50 to $150), plus either an automated scanner ($5 to $79) with pay-per-fix when something surfaces, or the bottom of the human watch market. The judgment call is how bad a bad week would be.

Revenue business, nobody technical on staff
Real revenue or real customer data, no in-house developer
$500 to $2,000/mo

Infrastructure ($100 to $300) plus a named human who monitors, patches, updates, and answers when something breaks ($300 to $1,500). At this profile the question is not whether to pay for care, it is who, and whether they will still be there in year three.

The new variable

Why AI-built apps break the standard advice.

Every maintenance guide on the first page of Google assumes your app was built by developers you can call. If yours came out of Lovable, Bolt, Replit, v0, or a long conversation with Claude, three things change the math.

There is no in-house developer. Traditional maintenance advice quietly assumes someone technical is already on payroll and maintenance is a fraction of their time. For an AI-built app the builder was a subscription, so any human attention is a new line item, not a reallocation. That is why this market is developing its own price list, covered below, instead of inheriting the agency one.

The unknown unknowns are worse. A human team leaves documentation, commit messages, and a person who remembers why. An AI builder leaves confident-looking code with no memory. The expensive part of maintaining it is not typing fixes, it is that nobody knows which parts are load bearing, which corners were cut, and whether the auth actually works, until someone reads it properly. This is why a one-time assessment before settling into a routine is worth more here than in any traditional codebase, and why we wrote a separate guide to handing off a vibe-coded app.

Month three is when it gets real. The pattern shows up in every founder forum: the build weekend is euphoric, month one is quiet, and around month three the first dependency breaks, the first weird bug appears, or the first user hits something the AI never tested. That is normal. It is not evidence your app is doomed, and it is not your fault the builder did not warn you. But it is your problem, and month three is exactly when a maintenance budget stops being theoretical.

The market, honestly

DIY, scanners, or a human: what each costs and buys.

Prices below were checked against each provider's live site as of July 2026. One disclosure up front: Continuum is our own service, so read that row knowing we have a horse in this race. The rest are genuine recommendations where they fit.

DIY, $0 plus your time. Free uptime monitoring, free-tier error tracking, backups on a calendar reminder, billing on your own cards. Genuinely sufficient for the hobby band, and the foundation everyone should have regardless of what else they buy.

Automated scanners, $5 to $79 a month. Vibe App Scanner sells $5 and $19 one-time scans and $29 a month continuous monitoring, with remediation referred out to a partner shop. Useful smoke alarms, honest about what they are. Worth knowing: detection is commoditizing fast, the builder platforms are absorbing scanning into their own products, so expect this tier to trend toward free. A scanner finds; it does not fix, and it does not judge.

Human care plans, roughly $66 to $3,499 a month. This tier is mature for older ecosystems and strangely empty for AI-built apps. WP Buffs has run WordPress care plans at $66 to $219 a month for years, proof the model works at small-business prices. In Rails, reinteractive's CodeCare and OpsCare offer fixed-price monthly maintenance and managed ops, and Planet Argon runs maintenance retainers for legacy apps; both are excellent if your app is Rails, which most AI-built apps are not. For AI-built apps specifically, as of July 2026: vibe-audit.com offers a $300 a month Ongoing Security Guard from a solo operator, Justin McKelvey takes retainers at $1,500 to $3,000 a month, 303 Software's Vibe Build and Vibe Live run $1,997 and $2,997 a month but are coaching and pairing rather than someone operating the app for you, and Afterbuild Labs' retainer is $3,499 a month for 40 hours. Between the $300 solo plan and the $1,500-and-up retainers there is very little productized, operated care, even though real buyers in founder forums post budgets around £500 a month total for business-critical AI-built apps. That gap is the honest summary of this market in 2026.

Where Continuum sits. Our recurring tiers live in that gap on purpose: Watch is always-on monitoring of the live app with plain-English, ranked alerts at $49 to $199 a month, and Care adds a named human who actually fixes the findings as they surface, each fix with a re-runnable proof, at $500 to $1,500 a month. Engagements usually start smaller: a free Leak Check that reads your live site from the outside, a $299 Ship Check audit if you want the full ranked picture, and fixed-scope Ship Fix work at $4,000 to $15,000 only if something serious is actually broken. Full menu on the pricing page. The model we are betting on is the one WP Buffs proved: most small apps do not need a $3,499 retainer or a rescue, they need a competent person who stays, at a price a small business can carry for years. How long clients actually stay is on the proof page.

And honestly: if your site is WordPress, go to WP Buffs, that is their home turf. If your app is Rails, reinteractive and Planet Argon have depth we do not claim. If you want intensive coaching to become the maintainer yourself, 303 Software's model fits that goal better than being operated for. And if what you actually need is ongoing technical leadership rather than maintenance, that is a different purchase with its own market, mapped in our fractional CTO pricing guide.

The honest section

When you do not need to pay anyone.

A maintenance page that never says "keep your money" is an ad. So: keep your money if the app has no revenue, no private user data, and downtime would cost you nothing but mild embarrassment. Keep it if the app is a static or nearly static site, where there is almost nothing to maintain. Keep it if your platform hosts and patches everything and you have never ejected from its defaults. Keep it if you are still building and pivoting weekly, because paying someone to maintain an app you are about to rewrite is burning the budget you will want later.

Do the free basics anyway, they take one afternoon: billing and domain on cards you own, two-factor everywhere, a free uptime monitor, a recurring backup, and a one-page inventory of every account and key your app depends on. That inventory costs nothing and is the single highest-value maintenance artifact you can create, as anyone who has read our developer-left guide can confirm. The moment real users, real money, or real data arrive, come back to the budget bands above. Not out of fear, just because the app will finally have something to lose.

FAQ

Maintenance cost, straight answers.

As of July 2026, infrastructure for a small SaaS app runs about $20 to $100 a month: hosting, a managed database, email, and a few third-party APIs. The bigger variable is the human. A hobby project can be maintained for nearly nothing. A side project with real users realistically lands at $100 to $400 a month once you add monitoring and occasional paid fixes. A revenue business with no technical person on staff should budget $500 to $2,000 a month for infrastructure plus someone who actually watches and fixes the app.
It is a reasonable planning heuristic for traditionally built software, where a $100K build implies roughly $15K to $20K a year of upkeep. It breaks completely for AI-built apps. If Lovable, Bolt, or Claude built your app for a few hundred dollars in subscription fees, 15 percent of that is around $5 a month, which will not cover your hosting bill, let alone a security patch. For AI-built apps, ignore percentage rules and budget from the actual cost drivers: infrastructure at $20 to $100 a month, plus whatever level of human attention your users and revenue justify.
Less than people fear. A typical AI-built stack in July 2026: Vercel Pro at $20 a month, Supabase Pro at $25 a month, a transactional email service at $15 to $35, a domain at about $1 a month amortized, and error tracking free or around $30. Free tiers cover genuine hobby projects entirely. Hosting only gets expensive with real scale, heavy media, or unoptimized AI API usage, and a runaway LLM API bill is the single most common cost surprise in AI-built apps.
Partly, and you should do the free parts regardless of who else you hire. You can keep billing and domains on your own cards, check uptime with a free monitor, read your error tracker weekly, and take regular database backups. What you cannot realistically do without technical skill is judge which dependency updates are safe, patch a security hole, or respond to an incident at 2am. DIY covers the watching half of maintenance reasonably well. It does not cover the fixing half, and the fixing half is where apps die.
A scanner is better than nothing and honestly priced for what it is. Tools in the $5 to $79 a month range, like Vibe App Scanner at $29 a month for continuous monitoring, will flag known vulnerability patterns and misconfigurations. What they do not do is fix anything, judge severity in the context of your business, or notice a category of problem nobody wrote a rule for. Scan prices are also falling toward zero as the app-builder platforms absorb detection into their own products. If your app has revenue or private user data, the scanner is a smoke alarm. You still need someone who shows up when it goes off.
Budget as if the build cost were irrelevant, because it is. Plan on $20 to $100 a month of infrastructure once you outgrow free tiers, then decide on human coverage. If the app has no revenue and no sensitive data, DIY plus a scanner is defensible. If it earns money or holds customer data, real buyers in this situation post budgets around $500 a month total, and as of July 2026 that buys either a light monitoring plan plus pay-per-fix, or the bottom of the human care market. One warning: get a one-time security review before settling into a routine, because maintaining an app that is already exposed is watering a garden with the gate open.
Nothing, for a while, which is what makes it tempting. Then things expire and drift: a card on file fails and hosting stops, a dependency develops a known vulnerability that attackers index, an API deprecates an endpoint, a growing table makes pages time out. Most neglected apps do not die dramatically. They die from a $12 renewal failure nobody saw, months after the last person stopped watching. The minimum viable maintenance is not zero, it is making sure someone notices when something changes.
A simple test: price the week of downtime or the data breach you could not shrug off. If the app makes $3,000 a month, a down week costs $700 and a breach could cost the business, so $500 a month for someone who prevents both is cheap insurance. If the app makes nothing and holds nothing sensitive, $500 a month is wildly premature and you should say no to anyone selling it to you, including us. Paid human care earns its keep exactly when the app has something to lose.

Want a number for your app,
not an industry average?

30 minutes, no pitch. Bring your current bills if you have them.Reads your live site from the outside. One minute, no signup.

If the honest answer for your app is DIY plus a $29 scanner, that is the answer you will get.

Matt

Last updated: July 2026. All provider prices checked against their live sites as of July 2026.