Payload CMS: The Headless CMS for the AI Age — and Your Data Stays in Switzerland

Payload is a so-called headless CMS — a system where content management and the visible website are completely separate. You manage texts and images in an admin interface, and that content can be delivered anywhere: website, app, or newsletter. Other headless CMS platforms work similarly.

What makes Payload distinctive: it is code-first. The content structure — which fields a page has, how sections interact — is defined in code, not assembled in a ready-made builder. For you, this means the website follows your processes, not the other way around. Payload is also open source and self-hostable — including on a server in Switzerland.

For SMEs, this means in practice: Payload gives you a great deal of room to tailor a website precisely to your business. That flexibility is real — but it requires access to developers.

The greatest advantage of Payload for SMEs is its flexibility. Many systems force you into a predefined structure — with Payload it works the other way: the platform can be shaped around specific needs with remarkable ease. A booking form, a custom calculation tool, a product database with specialist fields — whatever the business requires becomes part of the website, not an add-on bolted on alongside it.

This adaptability is also why Noevu uses Payload when a project needs more than a standard website. Rather than bending an off-the-shelf product until it approximately fits, a solution is built that is shaped to the client from day one. The price of that freedom: it has to be built — by someone who knows the platform. And this is where an often-underestimated lever comes in: because Payload lives in code, building custom features can be done with AI support. A calculator, a booking flow, or a specialised database take shape faster and more cost-efficiently than before.

Many CMS platforms are hurriedly stacking AI features on top. Payload goes further and openly positions itself as the CMS for the AI age — with two sides that matter to an SME: what AI the system brings, and how well you can work with AI alongside it.

The Enterprise edition includes a full AI toolkit — and in one area it goes further than most systems:

The second side is the real lever for Noevu. Because Payload lives in code, custom features can be built faster and more cost-efficiently with AI-assisted development than before. And because everything runs self-hosted, that AI power stays on your own infrastructure — unlike pure cloud systems, whose AI sends your content to a foreign provider. With Payload, AI capability and data sovereignty are not in conflict.

Here lies a second major advantage for Swiss SMEs: you can run Payload on your own server — including at a Swiss provider like Infomaniak or nine.ch. Self-hosting means your content and data stay where you decide, not in the cloud of a foreign vendor.

For Switzerland's revised Data Protection Act (revDSG, in force since September 2023), this is a plus. With many cloud services, data resides in the EU or the US. For most SMEs, the EU is unproblematic — Switzerland recognises it as a safe data territory. But in sensitive sectors such as healthcare, pensions, or finance, Swiss hosting is often required or clearly preferred.

That is precisely where the value of data sovereignty becomes clear. A self-hosted system on a Swiss server keeps sensitive data in the country — without routing it through a foreign cloud.

In Switzerland, multilingual support is rarely optional — it is a requirement. German, French, Italian — an SME website often needs all three. Payload has multilingual support built in: content can be managed per language without an additional plugin and without rebuilding the site three times.

In practice, this can be taken further. An integrated AI translation tool translates new content directly in the admin interface — at the click of a button, with a review-and-correction step before anything is published. For you, this means a new article is available in all languages within minutes, and quality control stays with you. Instead of commissioning each translation externally, it is produced in the same workflow as the original.

The same goes for images. Cropping, setting a focal point, managing alt texts per language — all of it sits directly in Payload, without an extra plugin. For you, this means an image is uploaded once and then fits every spot and every language, with no external tools.

One feature that makes a real difference in day-to-day editing is the live preview. While you are editing text, you see right next to it how the finished page will look — not a rough approximation, but the actual layout with your content. For you, this means fewer surprises after publishing and more confidence when editing, even for team members without a technical background.

This is where Payload plays one of its strengths. The live preview is deeply built into the platform and mature — a noticeable advantage over Strapi, where the same feature is less developed. Anyone who regularly manages content will notice this difference every day.

How these advantages combine in a real project is illustrated by a multilingual website Noevu is currently building for a Swiss SME client on Payload (in development — the name will follow when the project goes live). The project is a good example of what the platform makes possible in practice:

What stands out in the project: the platform can be shaped to specific needs without detours — from custom calculators to language logic. Payload is now used by Noevu across several projects, from Swiss SMEs to international presences. It is not the right tool for every website, but where individuality and data sovereignty matter, it plays to its strengths. If you are planning a similar project, it is worth exploring the possibilities of a custom-built website.

Payload is not the right tool for every situation. But there are clear scenarios where it plays to its strengths — and others where it is simply too much.

Payload fits particularly well when:

• Your website needs to do more than text and images — custom features, calculators, forms, databases
• Multiple languages are required and content changes regularly
• Data sovereignty matters — your data should or must stay in Switzerland
• You want AI features without sending content to a foreign cloud
• Your team has access to developers, internally or through an agency

Payload is less suitable when the website is modest in scope — few pages, rarely updated — or when no one can provide technical support for the setup. Those looking for an all-in-one solution without developers are better served by a builder like Squarespace.

Payload's pricing model looks unbeatable at first glance: the software is open source and free. But the license is only a small part of the total picture.

What does not appear on any price list:

• Website development: Payload delivers the content management layer — the visible website is built separately. Initial costs: roughly CHF 8,000–25,000 depending on scope.
• Setup and content structure: Because Payload is code-first, setting up the system and structuring content requires developer time.
• Hosting and operations: Server costs, updates, and security patches accumulate continuously — with self-hosting, that responsibility is yours.
• Enterprise AI: The full AI suite is paid — the free version relies on plugins instead.

Bottom line: the saved license does not mean the system is free. It shifts costs from the license to development and operations — but in return the solution is entirely yours.

Anyone evaluating Payload usually also looks at Strapi and WordPress — and if the goal is to work entirely without developers, Squarespace. The four systems follow very different approaches; the right choice depends less on individual features than on your situation.

The most important difference: Payload, Strapi, and WordPress require developers — but in return the solution is yours and can stay in Switzerland. Squarespace works without developers, but you give up flexibility, data sovereignty, and depth. Compared with WordPress, what stands out with Payload is cleanliness: no legacy baggage, no plugin sprawl, a well-structured foundation. There is no objectively best system — only the right fit or the wrong one.