One backend. As many websites as you need.
Every site gets its own design, its own domain and its own front end. They all share one backend, one login and one place for content.
~/solutions/multipressrunning
One WordPress. Every website.
The world’s most popular CMS, optimized and fine-tuned for AI. MultiPress is headless WordPress: one backend runs as many websites as you need. Every site has its own MCP server and its own front end, on whatever stack you choose.
Already have a site with me?Log in to MultiPress
what’s inside
MultiPress is WordPress, modernised: headless, multisite and ready for AI. The backend is done, so the work goes into your sites and your content.
Every site gets its own design, its own domain and its own front end. They all share one backend, one login and one place for content.
Templates, custom fields and content management are already built. You shape the front end; AI can set up the rest through MCP.
Updates, security fixes and new features go into one backend, not into one install per site.
Custom, native MultiPress multilingual features. No WPML, no bloat, just languages that work on every site.
Custom features, plugins, themes and small tweaks, so it fits how you work instead of the other way round.
Content, media and settings backed up on a schedule, and restored when you need them.
The whole backend ships as containers, so it runs the same on my servers or on yours.
custom fields
MultiPress runs on custom fields (ACF). Every page is a short form of plain, simple fields, so editing content is quick and the design you paid for stays exactly as it was built.
Every page is a short form: text, images, links and lists, each in its own field. Nothing to learn, nothing to drag around.
Design belongs to the front end, not in the WordPress admin.
Through the site’s MCP server, your AI agent knows the website structure, fields and templates, and manages them for you.
ai & agents
Humans edit in WordPress admin, AI agents via MCP. Tell your assistant what to change, and it’s live on your site a moment later.
Change text, prices, opening hours or images by telling your assistant what you need.
Each site has its own, so your agent always works on the right one.
Ask for the French page and it’s translated and live.
works with
network features
Integrations and features that live in MultiPress itself, ready for every site in your network. Turn them on for the sites that need them.
integrations
coming soonBuilt in, powered by HetrixTools. Activate it per site from MultiPress integrations.
for local businesses
coming soonNo third-party plugins, no extra subscriptions. Just activate them.
white label
MultiPress runs your whole network behind one login page, and that page wears your brand, not mine. Clients sign in on your domain and only ever see your name.
On the network's login page, where every client signs in.
So it looks and feels like your own product.
Something like login.your-brand.com, not mine.
After sign-in, each person sees only their own sites.
$ npx create-multipress-astro
Use any front-end stack you like. I provide an Astro starter tuned for MultiPress, so a new site starts with everything below already in place.
Claude Code or Cursor already know how a MultiPress site is built, so they build it the right way.
The content connection is already wired, so a new site starts with real content on day one.
The site and its MCP server are set in .env. Nothing else to configure.
astrostaticfasteasy to host
how it works
The backend is never on the front line. It can sit behind a VPN or be restricted to the people and places you allow, out of public reach. The sites only meet it when they’re built.
Headless WordPress holds the content, media, users and roles for every site. Editors and agents work there; visitors never see it.
When someone publishes, a build pulls that site’s content and turns it into a finished static site.
Each site has its own custom front end and its own domain. It’s served as static files, with server powers where it needs them.
The live sites have no database and no admin login, and they never talk to the backend.
Backend down for maintenance? Every site stays online, because each one is already built.
Updates, security fixes and new features go into one backend, not one per site.
open for projects
Tell me how many sites you run and who edits them. I’ll show you what MultiPress would look like for you.