Payload CMS, the way we run it ourselves.
We self-host Payload CMS in the EU and extend it with our own open source plugins, rather than just using it as-is.
Starting point
Sound familiar?
WordPress feels too narrow for your product
Because application logic and content editing belong together.
A SaaS CMS stores your data outside the EU
And you want to keep control over hosting and data yourself.
You want a framework without vendor lock-in
One your team can keep working with on its own, without us.
Payload CMS brings application and content editing together in one open, self-hostable system.
The result
You get Payload CMS the way we run it ourselves: self-hosted in the EU, extended with our own open source plugins, and open for your team.
- Self-hosted Payload instance on EU infrastructure
- MCP server plugin for AI assistants, write access limited to drafts
- Email adapter that sends transactional mail through Lettermint
- Fully open source, documented and free of vendor lock-in
Process
How we go about it
01 / FIT
We check whether Payload fits.
Payload fits applications with their own data model and editorial needs. For a handful of static pages, it is more than you need.
02 / SELF-HOSTING
We run Payload ourselves in the EU.
No SaaS layer in between: the instance runs on infrastructure you or we choose, with full control over the data.
03 / EXTENSION
We extend it with our own open plugins.
Among them an MCP server for AI assistants and an email adapter, both open source under abinnovision/payloadcms-commons.
04 / OPERATIONS
We document what belongs to it.
Code, configuration and the decisions behind them, so your team can keep running Payload without us.
Team shape, cadence and handover in detail are covered on the How we build page.
Questions
Frequently asked questions
An open source application framework built on Next.js that includes full content management from the start, instead of a separate CMS bolted on.
Because it fits our TypeScript stack, can be self-hosted, and we can extend it as open source without depending on a vendor.
Two packages under abinnovision/payloadcms-commons: an MCP server for AI assistants and an email adapter for Lettermint, both on npm.
It exposes a schema-aware tool surface. Write access is limited to drafts, and capabilities can be scoped per API key.
Not automatically, that depends on hosting. Self-hosted on EU infrastructure, the way we run it, that can be done cleanly.
Yes, that's our web development service: frontend, backend and content model as one system. This page explains Payload itself, not the finished project.
No. We do not estimate work we have not understood. An analysis always comes first.
No. Whoever starts stays until handover.
No. After handover you decide when we lose access to your systems. There is no spare key.
The code is yours and so is the documentation, entirely from day one. We do not build dependency on us as a business model.
Where this shows up in our work
Web development
For large, content-heavy websites with many pages and multiple editors, we build an enterprise CMS: frontend, backend and content model with Payload CMS as one system.
An MCP server plugin for Payload CMS. A schema-aware tool surface for AI assistants, with writes restricted to drafts and capabilities scoped per API key.
View on GitHubEmail adapter for Payload CMS. Sends transactional mail through the Lettermint API.
View on GitHubContact
Tell us how Payload fits your project.
Whether as a CMS for a new website or as a framework for your application, we'll tell you honestly if it fits.
André Loreth
Andreas Neugebauer
You talk directly to the founders.
A reply within one working day.
On the call
- 01You describe what's going on: a new system, or one that isn't keeping up anymore.
- 02We ask questions and tell you honestly whether and how we can help.
- 03You get concrete next steps, whether or not we end up working together.