Contact
Headless CMS

Contentplatformsfororganisationsthatwanttoremainincontroloftheircontentandthesourcecodebehindit.

We build headless CMS systems for editorial teams and business units that want to replace or rebuild an existing CMS without locking themselves into a vendor, plugin ecosystem, or fixed feature set. Content model, multilingual setup, role and approval logic, and the operating model are documented in writing before the first sprint. Fast loading times, technical SEO, and accessibility are part of the specification, not a later optimisation package.

Schedule a callSee solution formats ↓
EU hostingSource code ownershipPerformance & SEO as standardMultilingual in the content model

Engagement packages

Every package starts from a worked-out content structure.

Each package starts with a jointly worked-out content structure and a defined operating model, and we agree the success criteria, the multilingual scope and the editorial roles together with your editorial team before the first sprint.

2 – 3 weeks

Start here

CMS Audit

An inventory of your existing content, editorial workflows, multilingual structures, and technical dependencies. We assess what can be migrated, where structural groundwork is needed, and what feature scope is actually required in the successor system. The output is a written roadmap with a migration or build recommendation.

What's included

  • Content inventory of the existing site
  • Mapping of editorial workflows and roles
  • Assessment of multilingual setup and URL structure
  • Catalogue of technical dependencies and integrations
  • Risk assessment for migration and redirect strategy
  • Roadmap with a recommended next step

Best suited for

Organisations that want to replace an existing CMS but have not yet defined the scope, the risks, or the right shape of the successor system.

Discuss this audit
Standard site on a headless stack

Solution package 01

Standard site on a headless stack

1 – 2 weeks
Site with custom design

Solution package 02

Site with custom design

2 – 5 weeks
Headless platform with application logic

Solution package 03

Headless platform with application logic

6 – 14 weeks
Migration to headless

Solution package 04

Migration to headless

4 – 8 weeks
Operation and care

Solution format 05

Operation and care

Ongoing, monthly

Common questions

What decision-makers ask before a project begins.

These topics belong in the architecture before a single line of code is written. We address them systematically during content intake so they do not remain open questions during live operation.

  • Existing content is inventoried before a migration strategy is set. URL scheme, multilingual structure, and redirect list are mapped in writing. Migrations are executed with a documented rollback procedure and a defined go-live window.

Engagement model

How an engagement progresses.

Every engagement follows a documented path from content intake through to ongoing operation. Handovers to the editorial team take place in stages, with documented support.

01

Content intake

We map the existing content, editorial workflows, multilingual requirements, and interfaces to existing systems. The output is a documented content structure that serves as the basis for the architecture.

02

Architecture and specification

Content model, role and approval logic, multilingual scheme, URL structure, and redirect strategy are documented in writing before implementation begins. The operating model, hosting profile, and security requirements are part of the specification.

03

Build and editorial handover

Implementation proceeds in traceable steps. Before go-live, the editorial team is onboarded into the system in a documented session. Handover documentation, content model description, and operational notes are part of the delivery.

04

Operation

After go-live, we support the system at defined intervals. Security updates, platform care, and smaller enhancements follow a prioritised backlog. Larger changes go through the specification process again.

Delivery standards - What is included in every delivery.

The following properties are part of the standard scope of every content platform we build. They are defined during the specification phase and form part of every acceptance protocol.

Performance and SEO standards

Core Web Vitals, semantic markup, sitemap.xml, robots.txt, structured data, and Open Graph fields are part of the standard scope. Performance thresholds are documented per content type and verified before acceptance.

Multilingual setup in the content model

Language profiles, URL scheme per language, and translation workflows are part of the architecture, not a post-hoc translation layer. Content and structures per language are independently maintainable.

Accessibility to standard

Semantic markup, keyboard operability, contrast, and screen-reader compatibility are part of the specification. Components are checked against WCAG 2.1 AA criteria.

EU hosting and data residency

Hosting on EU infrastructure with a documented security and performance profile. On-premise deployment is possible where your own infrastructure exists. Data transfers to third-party clouds can be eliminated where privacy law requires it.

Role, permission, and approval logic

Editorial roles, approval paths, and permission assignment are defined before implementation. Content changes are logged and traceable.

Full source code in your hands

Source code passes to your ownership on delivery. Architecture and data are portable so that continuation by your internal team or another provider remains possible at any time.

Fit

When we are the right partner for your content platform.

We pick engagements on substantive fit, because a cleanly framed starting point is what lets a project actually deliver what was agreed at the beginning.

Well suited

  • 1You are replacing an existing CMS and want to migrate content, URL structure, and SEO rank in an orderly way
  • 2You operate a site with ongoing editorial need and multiple languages or locations
  • 3You want to keep content and source code in your own control rather than committing to a vendor, plugin ecosystem, or fixed feature set
  • 4You plan extensions that go beyond content presentation (e.g. member area, enquiry workflows, integration with existing systems)
  • 5You have a named internal editorial owner and a clear reason for the modernisation

Less suited

  • One-off marketing or campaign sites without ongoing editorial need
  • Standard shop solutions for which established products are a better fit
  • Engagements without a named editorial owner on the client side
  • Fixed-price expectations before an inventory of content and multilingual scope
  • Migrations where content structure, redirects, or multilingual setup are to remain unresolved

Next step

Let's walk through your initiative together.

Where a structured engagement begins

Start a project

Office

  • Karlsbad
    Auf der Hub 38
    76307 Karlsbad, Germany
  • Remote
    Distributed team
    Available internationally