Website and App Maintenance Costs After Launch

Many business owners budget for building a website or app but forget that, after launch, there are still running costs and maintenance work. The result: a domain that lapses, backups nobody checks, or a service that stops because a free quota ran out. This article covers what you need to budget for. We deliberately leave out prices, because third-party prices change often. Always check the provider's current pricing.

Running costs you'll almost always have

• Domain. Paid yearly. If it lapses, your website and email stop, and someone else can buy the domain.
• Hosting or server. A simple website often fits a small plan or free tier. An app with many users needs a bigger server.
• Database. Needed when there are user accounts, orders, or data that keeps growing. The cost usually rises with data size.
• Email. Two kinds: work email for your team, and an automated sending service for things like order confirmations.
• Third-party services. Payment gateways usually take a fee per transaction, AI services charge by usage, and file storage charges by size.

Maintenance work to budget for

• Security updates. The frameworks and libraries behind your site regularly release security fixes. Leave them for years and updating becomes harder and riskier.
• Backups and restore tests. Backups should run automatically, and every so often they need testing by actually restoring them.
• Error monitoring. Someone needs to know when something breaks, before customers complain.
• Bug fixes. However good the testing, real users will find cases nobody expected.
• Small changes. Update a price, add a promo page, tweak a form. Small jobs like these come up almost every month.

Static websites vs apps with a database

A static website is made of ready-built pages, with no login and no database. Few parts can break, so maintenance is light: renewing the domain, updating content, and occasional library updates. The website for Devans Egg, our client selling salted eggs and salted-egg crackers, is built as a static site like this.

An app with a database has many more moving parts: user data, payments, automated emails, and integrations. Each one can go wrong and needs looking after. It's normal for its maintenance budget to be much larger than a static website's.

Our experience at Numekara

Numekara, the education business we run, is an app with a database, logins, and payments. Some of the maintenance work we run there:

• Daily encrypted backups to separate storage, with restore drills into a test database whose results are recorded as evidence.
• Server error logging with correlation codes, on an admin page that also shows backup status, email usage, and database quota.
• Automated checks before release, which only run the checks for the parts of the code that changed, so CI minutes aren't wasted.

We also learned that free tiers have limits you have to watch. In early October 2026, our free GitHub Actions minutes ran out, and every scheduled job failed to run, including the daily backup. Afterwards we streamlined CI, made the automation schedule less frequent, and noted the need for a spending limit as a safety valve so backups don't quietly stop.

Another example: a web deploy once failed because the Worker bundle was 102 MB, over Cloudflare's size limit. We changed how large content is read, at build time instead, which brought it down to 16.6 MB and kept the site running on the same platform.

How to estimate a maintenance budget

1. Separate fixed costs from usage costs. Domains and hosting plans tend to be fixed; payment gateways, AI, and email grow with your customer count.
2. Check each service's free-tier limits, and what happens when you go over: it stops, slows down, or bills you straight away.
3. Set spending limits and alerts on services that support them.
4. Set aside developer time every month for updates, backup checks, and small changes, even when there's no new feature.
5. Ask for a written maintenance scope: what's included, how quickly problems are handled, and what counts as new work.
6. Review it every three to six months, especially after your user numbers grow.

When maintenance can be minimal

Not every business needs a monthly maintenance plan. A landing page or company profile whose content rarely changes may only need checking a few times a year. If you don't have a technical team and your needs are simple, a website builder that handles hosting and updates for you may suit you better. Regular maintenance becomes essential once your website stores customer data or takes payments.

You pay to build a website once. You pay to keep it running for as long as your business relies on it.