Maintenance and support from Vienna

Website maintenance: your site keeps running without you thinking about it

Most websites are built once and then left to themselves. A year later the security updates are outstanding, nobody has ever tested the backup, and load times have crept up. We take over day-to-day operations so that none of it is your problem.

  • Daily backups with tested restores
  • A contractual response time from one working day
  • Updates go to staging first, then live

This page describes day-to-day operations for a company website. Where that sits in the bigger picture is shown on the maintenance and support hub.

What does website maintenance cover?

Website maintenance is the day-to-day operation of a website: tested updates, daily backups, security measures, monitoring, and the administration of certificates and domains. On top of that comes an agreed monthly allowance for content changes. What the contract fixes is not only the scope of the work but also the response time when something breaks.

What happens when nobody maintains a site

Most successful attacks are not sophisticated. They hit unpatched installations: a plugin with a hole that has been public for months, a theme nobody updates any more. The second case is quieter, more common and more expensive: the contact form stops sending e-mails and nobody notices. Without monitoring and without a named owner, failures like that go undetected for months — along with the enquiries that never arrived in the meantime.

Then there is what expires quietly: an SSL certificate, a domain that was not renewed, a backup that has never been restored. Every one of those is avoidable, as long as somebody has it in the calendar.

What is included

Six areas are in every maintenance contract. What differs between the packages is the update frequency, the response time we commit to, how deep the monitoring goes and the change allowance.

  • Updates and compatibility

    Core, theme and plugin updates go into a staging environment first, where we check them before they go into production. Where there is a conflict, we come back to you rather than leaving a broken site behind.

  • Backups with tested restores

    We back up files and database daily and keep the snapshots for the agreed period. We test restores regularly, because a backup without a restore test is an assumption, not a safeguard.

  • Security

    We secure the login, set up two-factor authentication, limit login attempts, monitor for malware and harden the configuration.

  • Availability and performance monitoring

    We check availability every minute. If the site goes down, we get an automatic alert, usually before you notice anything yourself. We review the Core Web Vitals monthly and tell you what a drop came from: a new script, oversized images or the server.

  • SSL, domains and DNS

    We manage certificates, domain renewals and DNS records for you. An expired certificate is one of the most common avoidable outages there is.

  • Content changes

    Depending on the package you have one to four hours a month for text changes, new sub-pages or swapping images, with nothing to commission separately. You send us what needs changing; we do it and confirm it is done. If the allowance will not cover a piece of work, we say so beforehand — not afterwards on the invoice.

Which package fits your website

What you need depends on what an outage costs and on how much moves on the site.

  • Basic. For company websites that generate enquiries and are rarely rebuilt. Monthly updates, daily backups, availability monitoring and one hour of changes are enough here.
  • Business. For large WordPress installations with many plugins, where updates come round more often and conflicts are more likely. Updates run fortnightly and the response time drops to four hours.
  • Premium. For websites whose downtime costs revenue or enquiries immediately. Weekly updates, hourly database snapshots, interface monitoring and a one-hour response time.

If none of the three levels fits, because the site is really a shop or because several systems hang off it, we agree the scope and the response time individually.

WordPress maintenance and custom systems

Most of our maintenance contracts are for WordPress. We know the usual sources of conflict: page builders, outdated plugins and theme updates that overwrite custom work. How we build and take over such installations is described on the WordPress agency page.

Alongside those we maintain custom-built websites, where we also keep the frameworks and libraries in use up to date. Websites from our own web development move straight into this service after go-live, with no second round of familiarisation.

If you sell through the site, website maintenance stops at the shop boundary: order processes, interfaces and marketplaces belong to shop support. That holds for a WooCommerce shop too, even though it technically sits inside your WordPress installation.

What is not included

A maintenance contract keeps a website running; it does not replace a project. It does not cover third-party licence and hosting fees, the production of copy and images, or work that goes beyond the monthly change allowance. If the site needs a new structure, a new front end or additional features, that becomes a project of its own: a website relaunch or a job for web development.

If you permanently need more change hours than the package includes, we either bill the extra hours separately or move you up a package — whichever works out cheaper for you. We will tell you which of the two that is.

How maintenance starts

  1. Technical audit. We check the patch level, the plugins, the backups, the security posture and load times. If remedial work is needed, we say what it will take before the contract starts — not after.
  2. Settle the package and the response time. The audit shows which level the site needs and how many change hours a month are realistic.
  3. Handover. Access credentials, staging environment, backup targets, monitoring and alerting are set up, and the contact person is named.
  4. Ongoing operation. Updates go to staging first, then live. Reports follow at the agreed interval: quarterly, monthly, or monthly with a call.

Packages and response times

Every package includes a contractually agreed response time. The three levels differ like this:

Packages and response times
ServiceBasicBusinessPremium
Response time1 working day4 hours1 hour
Service hoursMon–Fri, 09:00–17:00Mon–Fri, 08:00–18:00Mon–Sat, 08:00–20:00
Updatesmonthlyfortnightlyweekly
Backupsdailydailydaily + hourly DB
Monitoringavailability+ performance+ interfaces
Changes included1 h/month2 h/month4 h/month
Reportingquarterlymonthlymonthly + a call

Hosting is optionally included: EU location, renewable energy. We work just as happily with your existing provider. The monthly amount depends on the level, the size of the installation, the number of plugins and interfaces, and the change allowance; you receive it as a quote after the first conversation and the technical audit.

Response time means a qualified reply from a developer, not an automatic acknowledgement of receipt. It runs inside the service hours of the level you are on — Basic Mon–Fri 09:00–17:00, Business Mon–Fri 08:00–18:00, Premium Mon–Sat 08:00–20:00; outside them it starts when they do. All levels and their service hours sit side by side on the maintenance and support hub.

Websites we did not build ourselves we take on after a technical audit; if remedial work is needed, we say what it will take before the contract starts. At the end of our work together we hand over access credentials, documentation and backups in full.

Measured results from live maintenance contracts — availability, load times, incidents headed off — are published in the Case Studies once the measurement period, the source and the client's approval are in place.

Frequently asked questions

  • What drives the cost of website maintenance?

    The system and the size of the installation, the response level you need and the monthly change allowance. Every package includes a contractually agreed response time. We name the monthly amount in a quote after the first conversation and the technical audit.

  • Which package does a WordPress website need?

    For most WordPress websites the Basic package is enough. Large installations with many plugins are better served by the Business package with fortnightly updates.

  • Do we really need a maintenance contract?

    If your website matters to the business: yes. Most successful attacks hit unpatched installations. And without maintenance nobody notices when the contact form stops sending e-mails. Failures like that often go undetected for months.

  • What happens if our website goes down?

    Our monitoring checks availability every minute and reports outages, usually before you notice anything yourself. After that the agreed response time applies: between one working day and one hour, depending on the package.

  • Do you take on websites you did not build?

    Yes, after a technical audit. If remedial work is needed, we tell you what it will take before the contract starts.

  • What if we need more changes than the package includes?

    Then we bill the additional hours separately, or you move up to a larger package — whichever works out cheaper for you.

  • Is hosting included?

    Optionally. We host in the EU on renewable energy, but we work just as happily with your existing provider.

The next step

For the first conversation, the address of your website and the name of whoever looks after it today are enough. Not sure what condition the installation is in? The free website analysis reports the patch level, the security posture and the three points with the greatest effect. Every other area is listed on the services hub.

Let us talk about your website

Thirty minutes with a developer. Afterwards you will know which package fits your website and what an audit is likely to turn up.

  • A contractual response time from one working day
  • Daily backups with regularly tested restores
  • If we host: EU location, renewable energy