Hosting is the cost that appears after the project is finished, was never in the quotation, and continues every month for as long as the application exists.
What a first-year application actually needs
Most early-stage business applications are far smaller than their owners expect. A system with a few hundred users doing ordinary transactional work runs comfortably on modest resources — the instinct to provision for scale that has not arrived wastes money that is better spent on features.
The components, and what each is for:
- Application server — runs the code. Sizing follows concurrent users, not registered users.
- Database — usually the component that matters most for performance and the one worth spending on first.
- File storage — user uploads, documents, images. Grows steadily and is cheap per unit.
- Domain and certificate — small annual costs, and the certificate must renew automatically or the site goes down on a predictable date.
- Email delivery — transactional mail needs a proper delivery service, because mail sent from an application server generally lands in spam.
- Backups — separate from the server, tested at least once.
Costs that are easy to miss
Quotations usually cover build. These recur:
- Hosting itself, monthly.
- Backup storage, which grows with data.
- Outbound data transfer, which can surprise for media-heavy applications.
- Email delivery, usually priced per volume.
- Push notification services, where applicable.
- Store developer accounts, annually, for native applications.
- Third-party API subscriptions — maps, SMS, AI services. Often the largest recurring item and the most variable.
- Monitoring and error reporting, which has free tiers that are usually adequate at first.
Asking a developer for the expected monthly running cost at year one and at ten times the usage is a reasonable request, and the answer tells you something about how carefully the architecture was considered.
Backups, and the part that gets skipped
A backup that has never been restored is a hypothesis. The restore is the thing that matters and it should be tested once before launch and periodically afterwards.
Three properties to specify:
- Frequency — how much data you can afford to lose. Daily backups mean up to a day's loss.
- Retention — how far back you can go. Important because some problems are discovered weeks later.
- Location — a backup on the same server is not a backup.
Monitoring
Two things are worth having from day one, and both have free tiers:
Uptime monitoring that alerts someone when the site stops responding. Without it, the first person to notice an outage is a customer.
Error reporting that captures application errors with enough context to diagnose them. Without it, "it didn't work" is all anyone can say, and reproducing the problem consumes more time than fixing it.
Who should hold the accounts
This is the point with the largest long-term consequence and the least attention at the time.
The client should own the hosting, domain and third-party service accounts, with the developer given access. Not the reverse.
When accounts sit in the developer's name, changing developers becomes a negotiation rather than a handover, and if the relationship ends badly the client can lose access to their own infrastructure. It is also a practical problem in ordinary circumstances — billing, renewals and recovery emails all go somewhere the client cannot reach.
Setting this up correctly costs nothing at the start and is awkward to unwind later. The domain in particular should always be registered to the client.
What to settle before build
- Where the application will be hosted, and in whose account.
- Estimated monthly cost at launch and at ten times the usage.
- Backup frequency, retention and location — and a restore test.
- Who is notified when the application goes down, and how.
- Which third-party services carry recurring fees and how they scale.
Related Manboo Services
- Flutter App Development for iOS and Android MVPs.
- Business Software Development for CRM, booking, inventory and workflow systems.
- Admin Panel Development for operations dashboards and backend management.
- AI API Integration when your product is ready for smart search, chat or automation.
- Request a scope review and project estimate when you are ready to plan the first version.