How much does website maintenance cost?

Your platform is live, people use it and something eventually needs attention. A software update, a failed background task or a bug can all interrupt work that was running normally yesterday.

A maintenance budget gives you a defined way to handle that upkeep. It should say what is covered, how much hands-on time is available and what happens when a problem needs more work.

The Aruno prices below exclude VAT and depend on an agreed scope. Your written agreement sets the service and payment terms; this is general information, not legal or tax advice.

How much does platform maintenance cost at Aruno?

The monthly range is for the upkeep of a custom platform, with a limited allowance for hands-on work.

Aruno custom-platform maintenance is typically €100 to €250 per month excluding VAT. It covers agreed dependency and security updates, uptime and error monitoring, and bug fixes within a total allowance of 2 hours per month. New feature development is separate.

Here is what that arrangement means in practice.

Included area	What it covers	Limit to understand
Dependency and security updates	Updates to the platform's supporting software	Hands-on work uses the shared allowance
Uptime and error monitoring	Checks and alerts for availability and recorded errors	Monitoring isn't a promise of constant human supervision
Bug fixes	Correcting agreed faults in existing behaviour	Hands-on fixes use the same allowance
Monthly hands-on allowance	2 hours across the included work	Extra work is discussed and quoted before proceeding

Updates, investigating alerts and fixes share two hours; each row doesn't get its own allowance.

The price depends on the agreed upkeep. Monitoring can run automatically; investigation and changes use hands-on time. Agree how time is recorded and whether unused hours carry over.

Which sites is this maintenance range for?

Match the support arrangement to the kind of site you actually have.

This range covers custom platforms, such as a portal with accounts and a team workflow. Scope and access need reviewing before we take on an inherited platform.

Marketing websites and landing pages don't have an ongoing maintenance plan. Hosting is agreed; later changes are separately scoped. See those services on the Aruno website.

Shopify and MerchantPro subscriptions cover a different service. The provider runs parts of the store's infrastructure; product changes, apps and custom work still need an owner.

For custom-coded site repairs outside a maintenance agreement, we quote according to the problem's seriousness. We don't repair Framer, Webflow or other builder sites; those requests can become a rebuild discussion instead.

Aruno builds include 30 days of bug fixes after launch, separate from continuing maintenance or new functionality.

What does a two-hour allowance look like?

A small monthly allowance works best when the tasks are clear and the platform is already in a manageable condition.

For an illustrative month, checking an alert might take 20 minutes, reviewing and applying updates 50 minutes, and fixing a small fault another 50 minutes. That uses the two hours. It isn't a promised monthly checklist or a guarantee that every update and bug will fit.

Some updates need more testing or platform changes than others. A short error message can hide a long investigation; apparent size doesn't determine repair time.

When the allowance runs low, you should know what was done and what remains. At Aruno, extra work is agreed and quoted before proceeding.

If a contact flow breaks, describe the exact steps and expected result. Our guide to forms that aren't sending emails shows why “the form is broken” isn't enough to locate the failure.

What is separate from maintenance?

Work that changes what your platform does needs its own scope.

Adding staff roles, a reporting screen or a new approval step is feature development. So are a redesign and a new integration. Calling them “small changes” doesn't make them upkeep, particularly when they affect several screens or business rules.

“An approved request doesn't appear” may be a bug. “Managers should approve requests in groups” is new behaviour to build.

Hosting, domains and paid services should be listed separately in your agreement. Backups and recovery aren't included in the stated maintenance range unless separately agreed. If losing records would disrupt your work, name who owns backups, how restoration is checked and what recovery support would cost.

Don't assume an unlimited emergency service either. Agree contact channels, support hours and response expectations. An automatic alert can arrive at any hour without meaning a developer is committed to respond immediately.

If your custom platform needs a predictable upkeep arrangement, we can discuss a maintenance scope. We'll talk about the platform, access, monitoring and the work allowance; investigations and repairs are paid work. Book a free intro call with no commitment, or contact hi@aruno.studio, WhatsApp or Telegram @mihaipostelnicu.

What should you check before paying monthly?

The useful comparison is the written service you receive, not the word “maintenance” beside a fee.

Ask for direct answers to these points before signing.

Question	Why it matters	What a clear answer names
What uses the allowance?	Investigation can take time before a fix exists	Updates, checks, investigation and fixes
When will someone respond?	Monitoring and response are different	Support hours and agreed response expectations
How are extras handled?	A fault may exceed the included time	Quote and approval before further work
Who holds the accounts?	Missing access can stop a repair	Hosting, code, domain and service access
Who owns recovery?	Monitoring can't restore lost data	Backup and restoration responsibilities

Use the answers to compare offers that cover the same platform and responsibilities.

A cheap plan may cover a narrow job. Watch for undefined “unlimited fixes”, unexplained allowances or reports that don't name what changed.

Keep previous tests to help spot changes after updates. Our guide to slow websites on mobile covers useful checks; a platform may also need investigation beyond a public speed test.

Frequent new requests may suit a separate development arrangement. Aruno's €2,000 monthly partnership, excluding VAT, has one active request at a time.

Frequently asked questions

These answers clarify the boundary between maintaining a platform and developing it further.

How much does Aruno platform maintenance cost? The indicative range is €100 to €250 per month excluding VAT. The agreed package covers updates, monitoring and bug fixes with a shared two-hour monthly hands-on allowance.

How quickly will a maintenance problem be fixed? There isn't one fixed time for every fault. Response expectations belong in the agreement, while investigation and repair time depend on the issue and available access.

Is a maintenance plan worth it? It can be if your team relies on a custom platform and you need regular upkeep plus a clear route for reporting faults. Compare that need with the included time and responsibilities.

Does maintenance include new features? No. New screens, workflows and integrations are separately scoped development, even if they sound small when described.

What happens if a fix takes more than two hours? We discuss the remaining work and quote it before proceeding. The monthly fee isn't a promise that every fault can be solved within the allowance.

List what your platform must keep doing and who is responsible when it stops. That gives your monthly maintenance budget a useful purpose.