Maintenance you only notice once it is missing
Security updates, backups and uptime checks run in the background, so your website never becomes your problem.
A website nobody maintains does not decline slowly. It runs quietly for months and is then gone on a Tuesday morning, because a dependency carried a long-known hole and an automated scanner found it. The damage is rarely the repair, it is the week in which your customers find nothing about you.
That is why maintenance here is not a line you can cut to save money. Updates, backups and uptime checks run whether or not anything happened last month. It is unspectacular, and that is exactly the point.
Who this suits
A fit if
- Your website brings in enquiries, so downtime is not an option
- Nobody in the building is watching updates and backups
- When something breaks you want a name, not a ticket number
Not a fit if
- Your IT department already handles updates and backups
- You expect an uptime guarantee backed by contractual penalties
- You want us to maintain a third-party system we are not allowed to change
What is included
- Security and dependency updates, applied and then checked in the browser
- Regular backups with a restore path we actually test
- Round-the-clock uptime monitoring: the alert reaches us, not you
- Certificates and domain renewals happen before anyone gets a reminder notice
How we work
- 01
Ongoing updates
Every month we check framework, libraries and server side for open security advisories. Anything flagged critical goes in immediately, the rest is bundled so the live site is not touched every week.
- 02
Backups and verification
There are backups of the files and of the content, and there is a tested way back. A backup that has never been restored is a claim, not a backup.
- 03
When something breaks
If something fails we hear about it first and get in touch before you notice yourself. Afterwards you get a plain account of what caused it and what stops it happening again.
What it costs
Included at no extra cost
Maintenance and security are part of the care contract that starts at go-live: from 49 euros net per month for hosting and technical maintenance. Content changes are not part of it; they are billed one by one, by effort. We do not sell it as a separate package, because a website we built should be kept current by us. The rights to the website - with the one-off price on final payment, with instalments on the last one - are yours, no matter who looks after the site later.
See pricingCommon questions
How fast do you react when the website is down?
The monitoring alerts us, not you, and we start with the cause rather than with a ticket. We do not put a fixed number of minutes in the contract, because the cause decides the duration: a data centre outage means reporting and waiting, a bug in our own code means a deploy.
What exactly is being updated?
The framework the site runs on, every library it pulls in, the server environment and the certificates. After each update we check the site in a browser rather than updating blind and hoping. We announce major version jumps in advance, because they take time.
Do we need maintenance if the website runs without a database?
Less, but not none. A site without a database and without a login has a far smaller attack surface than a typical WordPress install. Certificate, domain, form handling and the libraries in the build are still things that expire, change or develop holes.
Can we end maintenance?
Yes, the care contract is a separate, open-ended agreement with four weeks' notice to the end of a month. There is one exception: if you pay for the website in instalments, you keep the care contract for as long as they run. After cancelling, you take over yourself, and we hand across code, access and documentation. We also tell you what becomes your responsibility, so the decision is made with open eyes.
Further reading
- Website Maintenance in 2026: What It Costs and What Must Be In ItWhat website maintenance actually covers, what the market charges for it, and how to spot an empty maintenance contract before you sign it.
- HTTPS Is Not Enough: HSTS, Certificate Transparency and HTTP/3Why HTTPS alone does not protect against downgrade attacks, why HSTS preload is practically irreversible, and what HTTP/3 actually delivers.
- Core Web Vitals 2026: What the Three Numbers Really Mean for RankingThe current target values for LCP, INP and CLS, the most common causes of poor scores, and a plan to get your Core Web Vitals into the green.
- Lighthouse vs. PageSpeed Insights: A Score of 100 Proves NothingWhy a perfect Lighthouse score says nothing about rankings, what actually separates lab and field data, and which tool is responsible for what.
- Page Experience in 2026: Why Real User Data Wins, Not a Lab TestPage Experience runs on field data from real visitors, not a Lighthouse score. The signals, the correct target values, and why it is mostly a tie-breaker.
Let us talk about Maintenance and security
A conversation where we listen first and then say honestly whether and how we can help.
Message us on WhatsApp