Website support after launch: what's included and what it costs

Launching a site isn't the project's finish line but the start of running it. Without regular attention even a well-built site gradually accumulates problems: outdated dependencies, forgotten backups, small errors nobody notices until they turn into large ones.

What support usually covers

• Updating the platform, libraries and security modules.

• Regular backups, and checking that they actually restore.

• Monitoring the site's availability and speed.

• Tracking the domain and hosting and renewing them in time.

• Small content and layout fixes that don't warrant a full change project.

• Response to technical failures within agreed timeframes (an SLA).

Why you can't just "leave it running"

A site without support isn't a static object but a system living in a constantly changing environment: browsers update, search engines change their requirements, vulnerabilities are found in the libraries it uses. After a few months of neglect the difference between a maintained and an abandoned site becomes visible even to an ordinary visitor — never mind the security risk.

What the cost of support depends on

Price usually depends on the site's complexity, the volume of monthly changes, the response time required for critical issues, and whether the package includes proactive monitoring or only reaction to reported problems. It's sensible to establish in advance what happens when the included hours for a month run out, and how work beyond them is charged.

How to tell current support isn't enough

• Clients notice problems on the site before the business does.

• Small content fixes wait for weeks.

• Nobody can say when the platform and its components were last updated.

• The domain or hosting has already come close to expiring once.

If a site has been running unattended for a while, or the current support doesn't cover what you actually need, we can take it on with a clear list of what's included and defined response times.