Your agency for the Weblication CMS

Weblication is a German content management system that is sold and deployed almost exclusively through agencies. That has a pleasant effect – the installations tend to be stable and cleanly built – and an unpleasant one: when your agency disappears, there are not ten thousand freelancers around the corner like with WordPress. Which is exactly why websites regularly land on our desk whose owners searched for months without finding anyone.

We are not a content-upkeep shop that only pastes in text. We are software developers – and you notice that exactly where it hurts: a version update stuck on old templates, a form whose emails end up in spam, an interface to your ERP or applicant management system, server configuration and DNS. Those cases are why people search for a Weblication agency in the first place – not the tenth image gallery.

On top of that comes honest judgment: we tell you when a change is not worth the effort, when a relaunch beats the next band-aid – or when Weblication simply is no longer the right base for your plans. You get one dedicated contact person who knows your project instead of a ticket system with rotating agents. We are based in the Upper Palatinate and support clients across Bavaria and beyond – most of the collaboration happens remotely anyway.

Concretely, Weblication competence means this: we work in CORE and in GRID. CORE is the single-project license that the vast majority of company, association and municipal sites run on; GRID is the multi-project platform for many editors and high traffic. The difference decides whether a requested feature is configuration or development – and we clarify that before the quote, not after.

On versions, 21 is current (July 2026); version 20 had brought an AI search module, a plain-language module and dedicated accessibility tooling. Weblication is unusually far backwards-compatible – version 21 opens projects going back to version 5, so 16 years. A jump across several major versions is therefore not a rebuild but a plannable update. We know the two places where it still gets stuck: the server's PHP version (Weblication has required at least PHP 8.1 since version 17, with 8.2 or newer being sensible) and old BASE Classic templates, which unlike the newer mobile-first templates need manual work.

A takeover always follows the same programme: take stock of license, version, template generation, modules and hosting; update on a copy first, never live; then document the access credentials so you are not starting from zero at the next handover. That is exactly where most orphaned installations fail – not on the CMS.

And because "reliable" is a word every agency writes about itself, here are the commitments you can actually verify: the license runs in your name, not ours – we work inside your installation, not our own. Access to license management, hosting and domain belongs to you and is handed over documented, even if you move to someone else one day. There is no minimum term: you can book us on demand or take out fixed maintenance, and either can be ended. And you write directly to the developer doing the work – there is no intermediate layer here that passes your request along.