Payload runs on servers in Switzerland that you own or choose. The editorial system is part of your application: calculators, portals with login, forms and multilingual content in one interface.
Use case
When Payload is the right choice
Payload fits when your website has to do more than show text and images. That includes a calculator that computes benefits live, a customer portal with login, or forms connected to your database. All of it lives in one application together with the editorial system, on a server you choose.
Payload is one of three systems in Noevu's line-up. The headless CMS overview sorts Payload, Sanity and Strapi by data location, editing experience and operating model. What sets Payload apart technically is covered in the in-depth article on Payload CMS.
More than a website
What gets built with Payload
Portals with login
Customers, members or partners sign in and see their documents, contracts or appointments. Payload handles roles and permissions itself, with no extra system alongside.
Calculators and forms
A calculator shows the result while the visitor types. Forms write straight into your database, and every entry is available to the team in the editorial system.
Multilingual platforms
German, French and Italian in one interface: every page has its translations, AI drafts them, and your team reviews and approves before anything goes live.
Reference
Pension platform for VRM Gebäudetechnik
VRM Gebäudetechnik launched in 2026 as a pension foundation with no website. Its model is one two audiences first need to understand. The result is a trilingual platform on Payload: real-time calculator, 118 searchable questions, documents and news, all maintained by the foundation's own team. The data sits on a server in Switzerland.
How fast the platform loads is documented with the measurement date in the overview of Noevu websites.
The framework
Licence and data location
Licence: MIT
Data location: your server
Build, operations, design framework
The visible website is built with Astro or Next.js, depending on how much interaction and speed you need. How fast such sites load is shown in the website overview, with measurements and dates.
The process
How your Payload platform comes together
First call and prototype
See it before you decide.
The first call clarifies goals, audiences and data flows. From there a clickable prototype with real functions takes shape before any contract is signed. At VRM Gebäudetechnik it already included the calculator. You decide on the basis of a working website.
Data model and input forms
The system takes your shape.
Pages, documents, news, FAQ: every content type gets its fields and rules. Roles, permissions and languages are part of the model from day one. In parallel, the visible website is built with Astro or Next.js, inside your brand's design framework.
Content and translation
Your team takes over.
Your team maintains content with live preview, AI drafts the translations, and approval happens in the editorial system. A short handbook and an introduction are enough to get started. At VRM Gebäudetechnik the entire website was translated into French and Italian in a single day.
Launch and further development
Going live is the beginning.
After launch the platform keeps growing: a search, a portal or a new language are added as extensions. Smaller adjustments are covered by the service package, and updates and security run as part of the hosting. At VRM Gebäudetechnik the FAQ search was live a few days after the request.
Your Payload platform starts with a conversation.
A first call clarifies whether Payload fits your project and what a first prototype could look like. A binding fixed-price quote follows.
Brilliant — I'm really happy, the site looks fantastic. After an intensive and exceptionally productive collaboration everything runs smoothly; the new website presents the foundation in a modern, accessible way. Many thanks for the enormous effort — much appreciated.
Articles and projects on Payload CMS
Payload in practice.
The in-depth article on Payload and the VRM Gebäudetechnik project report show how the system works day to day.
ProjectWeb design7 minReady before signing — the new platform for VRM GebäudetechnikVRM Gebäudetechnik launched as a new pension foundation with no website — and a model two audiences first need to understand. A working prototype built before the contract was signed became a trili…
ArticleWeb design12 minPayload CMS: The Headless CMS for the AI Age — and Your Data Stays in SwitzerlandPayload CMS openly positions itself as the headless CMS for the AI age — with built-in AI features and an open interface for AI assistants. For an SME, what matters is not the hype but what remains…
All posts Answers about Payload CMS
What sets Payload apart from Sanity?
Payload runs self-hosted on a server you choose, while Sanity stores content in the vendor's cloud. With Sanity the Studio is open source, the backend stays proprietary, and an EU data centre is available. In return, Sanity offers visual editing directly on the page and a faster build. Payload pays off when calculators, portals or forms are part of the application, or when the data has to stay in Switzerland. The headless CMS overview puts both systems and Strapi side by side.
Where does the data live with Payload?
On the server you decide on. Payload is self-hosted: content, user accounts and form entries sit in your database, for example with a Swiss provider such as Infomaniak. The editorial system itself needs no third-party cloud. For sectors such as pensions, healthcare or finance this is often a requirement; for everyone else it is a piece of independence. Noevu runs the server as part of the hosting, or your IT team takes it over if you prefer.
Who maintains the content after launch?
Your team, without developers. The agency handles the build: data model, input forms, design and the visible website. After that your team maintains pages, news, documents and translations on its own, with live preview and draft status. The design framework acts as protection: colours, grid and typography are predefined, so the look stays consistent no matter who writes. At VRM Gebäudetechnik the foundation's own team maintains the platform in three languages.
What happens when the platform needs to grow?
The platform grows with you. New functions such as a searchable FAQ, a customer portal or another language are added as extensions, without rebuilding the system. Smaller adjustments are covered by the service packages at no extra budget. Updates and security run as part of the hosting, and Noevu monitors the system proactively with AI support. At VRM Gebäudetechnik the requested FAQ search was live a few days after the request.
What does a website with Payload cost?
Building a Payload platform starts from around CHF 8'000. The price depends on the data model, functions such as a calculator or portal, and the number of languages. The software itself is free, with no licence fees. Hosting and operations come on top as a running cost. Every project gets a binding fixed-price quote, so the scope is settled before work starts. A prototype ahead of the quote shows you what you are paying for.
