You are here: Website Maintenance > Ongoing operation

Author: (with the help of ChatGPT) | Reading time approximately: 3 min | last modified: 27.05.2026

Ongoing Operation of the Website

Two Fundamentally Different Models

Most websites are based on a classic setup:
An agency creates the site, an external host provides the server, and maintenance and updates are handled via additional tools or service providers.

The result is a distributed system without consistent responsibility.

However, there is also another model where development and operation come from a single provider. In this case, the web agency that creates the website also operates its own servers. The advantage is that there are no further parties involved and no separated responsibilities.

What the Difference Means in Practice

With the classic model, problems typically arise exactly at the interfaces:

unclear responsibilities in case of errors
delays due to forwarding between service providers
hard to trace causes in case of technical malfunctions
dependency on combinations of plugins, CMS, and hosting

In the event of an error, you as a customer often cannot determine who is actually responsible - and thus also not who has to take action to solve the problem.

Our Approach

Our approach eliminates these interfaces. We not only create your website, but also operate it on our own servers. If a problem occurs, both the cause and the solution are our responsibility and we are accountable for fixing it. You don’t have to worry about finding the right contact person.

Operation Instead of Handover

Many websites are effectively “handed over” after creation. After that, a separate maintenance process begins, which often only works reactively.

We actively continue to operate websites:

Hosting on our own systems
Ongoing technical maintenance
Direct interventions without external coordination

This is not an additional service, but part of the model.

Automated System Checks

Often, a website is created once and then no longer given much attention. After going live, the agency’s job is considered done. What happens during ongoing operation is not further monitored. Standard CMS environments usually only respond when something is visibly broken.

The lilac-CMS continuously checks central functions:

Forms and email delivery
Background system communication
Content changes with legal relevance (e.g., data protection)

The goal is not control but to prevent downtime during ongoing operation.

Security Without Plugin Dependency

Many common systems (especially plugin-based CMS) create their own complexity:
more extensions - more dependencies - more potential security vulnerabilities.

We reduce this complexity through a system consistently managed by lilac-media:

centralized updates
uniform technical base
no uncontrolled plugin landscape

The result is a system that is not “patched together,” but is operated consistently.

Conclusion

You can have a website made of many individual parts – or a system that is operated as a single unit.

The difference doesn’t appear at launch, but during ongoing operation: stability, response time, and responsibility.

We’ll show you how we support you even after your website goes live.

All About Operating Your Website