How much does app maintenance really cost after launch?
Most answers to this question give you a percentage of the build cost and stop there. The honest answer is that maintenance is three different bills sharing one name. One is compulsory, one is small, and one is not maintenance at all. Knowing which is which is most of the saving.
App maintenance after launch is three costs: the monthly running bill for hosting, database and services, which for a launched MVP is often under $100 a month before AI usage; the work of keeping the app compatible, secure and in the stores, which is compulsory; and new features, which are product development, not maintenance. Budget for the first two, and price the third as its own decision.
What does "app maintenance" actually include?
The word gets used for everything that happens after launch, which is why quotes for it range so widely. Split it into three and each part becomes something you can price:
| Bucket | What it is | Optional? |
|---|---|---|
| 1. Running costs | Hosting, database, authentication, email, store fees, AI usage. A bill from vendors, not from developers | No, but small at launch |
| 2. Keeping it alive | Platform and SDK updates, dependency and security updates, bug fixes, monitoring, store compliance | No. Skip it and the app degrades |
| 3. Improving it | New features, redesigns, new integrations driven by what users do | Yes. This is a product decision |
Much of the confusion comes from quotes that roll all three into one monthly number. A retainer that includes "a few new features each month" is mostly bucket three, and you are entitled to see it priced that way.
How much are the running costs?
This is the part founders are least often told, so Foundreco publishes typical ranges on the pricing page. For a launched MVP, hosting, database, authentication and email each tend to sit between free and about $25 a month, payments cost a percentage per transaction rather than a fixed fee, and AI features are the line that surprises people, anywhere from $5 to over $200 a month depending on usage.
The store accounts are fixed and public. The Apple Developer Program is 99 USD per membership year, and a Google Play developer account carries a US$25 one-time registration fee. A web app pays neither.
Running costs scale with users, not with time. At ten users they are close to nothing; at ten thousand they are a real line in your accounts. That is why the number should be written down before you build, with the assumptions behind it, rather than discovered from the first invoice.
What is compulsory, and why the platforms decide it
Bucket two is the one that cannot be skipped, and the reason is that the ground moves under a finished app. Three examples, each from the vendor's own documentation:
| What moves | The rule | What it means for you |
|---|---|---|
| Apple | Since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using an iOS 26 SDK | An app built on an older toolchain cannot ship even a one-line fix until it is brought up to date |
| Google Play | From 31 August 2026, new apps and updates must target Android 16 (API level 36), and existing apps must target at least API level 35 to stay available to new users | Leave an Android app alone long enough and new customers on current phones stop being able to install it |
| Your server runtime | A Node.js long-term support line typically receives critical fixes for a total of 30 months, and production apps should only run supported releases | A backend untouched for three years is running software nobody is patching |
None of this is a developer inventing work. It is a calendar, set by Apple, Google and the open-source projects your app is built on, and it arrives whether or not you have users. Add the ordinary work of fixing bugs real users find, renewing certificates and domains, and watching error logs, and you have the compulsory part of maintenance.
Why the "15 to 20% of build cost" rule misleads
Most articles on this topic quote a rule of thumb: budget 15 to 20% of the original build cost every year. It is easy to remember and it is the wrong shape. It assumes maintenance scales with what you paid to build, when it actually scales with how much surface the app exposes to change.
A modest app with payments, an AI feature and releases on iOS and Android has three platforms and two third-party integrations that can each change underneath it. A larger internal web tool with no store listing and no external services can go months without needing anything. The first may cost less to build and more to keep alive. What actually drives the number:
The last one is the lever founders control before launch rather than after it. Code that arrives with tests, documentation and a clean structure is cheaper for anyone to maintain, including a developer you have not hired yet. Code that only its author understands is expensive to maintain for as long as you own it. If you have inherited an app and are not sure which one you have, the free AI-app production readiness audit asks sixteen questions and ranks what is wrong by severity.
Who should maintain the app?
There are four realistic options, and the right one depends far more on how often the app changes than on its size:
| Option | Works well when | Watch out for |
|---|---|---|
| The original builder, monthly | The app changes often and you want one team accountable | A retainer that auto-renews, or one with no written list of what it covers |
| The original builder, as needed | The app is stable and only needs the platform updates above | Response times, which nobody has promised you |
| A freelancer or your own hire | You are building an in-house team anyway | Only realistic if the code and accounts are already yours |
| Nobody | The app is a prototype you are willing to let lapse | Store removal, unpatched dependencies, a fix you cannot ship when you need one |
The third option only exists if the code is in your repository and the store, hosting and database accounts are in your name. That is decided in the contract, before the build, which is why it appears in six clauses to look for in a software development contract.
What should a maintenance agreement say?
If you do agree monthly support, with anyone, these are the lines worth having in writing:
| Ask | A good answer |
|---|---|
| What is included? | A written list: platform updates, dependency and security updates, bug fixes, monitoring, store compliance |
| What counts as a new feature? | A clear line, with features quoted separately before they are built |
| How fast do you respond? | A stated response time for something broken in production |
| How do I cancel? | Monthly, with no notice period and nothing held back |
| Who holds the accounts? | You do. The supplier has access, not ownership |
One honest caveat: if your business needs a guaranteed round-the-clock response written into a service-level agreement, say so explicitly to every supplier you speak to, including Foundreco. A monthly retainer and a 24-hour on-call contract are different products, and a quote for one is not a quote for the other.
How Foundreco handles maintenance
To be specific about it, since this is our own blog. Before you sign, you get a written running-cost sheet: hosting, database, email, storage, store fees and any AI usage, line by line, with the assumptions shown. After launch, the first 30 days of bug fixes and store-compliance care are included at no charge, and there is no auto-renewing retainer waiting at the end of them. Both are clauses in the contract, set out on the guarantees page.
After those 30 days you have a choice rather than a default. The code is in your repository from the first commit, so you can take it to your own team. You can ask for work as you need it, quoted against the job. Or you can take a monthly maintenance retainer, from $600 a month and cancellable any time. Many clients need nothing ongoing, and the process page says so at step nine. If you are still at the stage of planning a launch, the free launch checklist covers what to have in place before users arrive.
Common questions about app maintenance costs
How much does it cost to maintain an app per month?
Can I stop paying for maintenance once the app is finished?
Is maintenance cheaper for a web app than a mobile app?
What is included in the 30 days of care after a Foundreco launch?
Why do maintenance quotes vary so much between agencies?
Know the monthly number before you build
Every Foundreco build comes with a written running-cost sheet before you sign, 30 days of care after launch at no charge, and no retainer unless you ask for one. Send your idea in three sentences to start.