~/solutions/multipressrunning

MultiPress

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.

what’s inside

Everything a website needs is already built.

MultiPress is WordPress, modernised: headless, multisite and ready for AI. The backend is done, so the work goes into your sites and your content.

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.

No backend code to write

Templates, custom fields and content management are already built. You shape the front end; AI can set up the rest through MCP.

One codebase to maintain

Updates, security fixes and new features go into one backend, not into one install per site.

Multilingual out of the box

Custom, native MultiPress multilingual features. No WPML, no bloat, just languages that work on every site.

Flexible where you need it

Custom features, plugins, themes and small tweaks, so it fits how you work instead of the other way round.

Backups

Content, media and settings backed up on a schedule, and restored when you need them.

Docker deployment

The whole backend ships as containers, so it runs the same on my servers or on yours.

custom fields

Edit the content. Not the design.

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.

  • Custom fields, not a page builder

    Every page is a short form: text, images, links and lists, each in its own field. Nothing to learn, nothing to drag around.

  • The design stays put

    Design belongs to the front end, not in the WordPress admin.

  • Your agent knows the fields

    Through the site’s MCP server, your AI agent knows the website structure, fields and templates, and manages them for you.

ai & agents

Update your site by asking.

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.

  • Ask in plain words

    Change text, prices, opening hours or images by telling your assistant what you need.

  • One MCP server per site

    Each site has its own, so your agent always works on the right one.

  • Every language

    Ask for the French page and it’s translated and live.

works with

  • Claude
  • ChatGPT
  • Cursor
  • n8n
  • your own bot
  • + any MCP client

network features

Built in. Just switch it on.

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 soon

Uptime Monitoring

Built in, powered by HetrixTools. Activate it per site from MultiPress integrations.

  • client-a.com
  • client-b.com
  • your-brand.com

for local businesses

coming soon

MultiPress native plugins

No third-party plugins, no extra subscriptions. Just activate them.

  • CheckoutSell straight from your website.
  • Services bookingClients pick a service and a time.
  • Events & ticketsFor bands, groups and artists.

white label

Your name on the door.

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.

  • logo

    Your logo

    On the network's login page, where every client signs in.

  • colours

    Your colours

    So it looks and feels like your own product.

  • domain

    Your domain

    Something like login.your-brand.com, not mine.

  • one door

    One login, every site

    After sign-in, each person sees only their own sites.

$ npx create-multipress-astro

Astro Front-End.

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.

  1. Skills for AI coding agents

    Claude Code or Cursor already know how a MultiPress site is built, so they build it the right way.

  2. A connector to the backend

    The content connection is already wired, so a new site starts with real content on day one.

  3. Keys in one file

    The site and its MCP server are set in .env. Nothing else to configure.

astrostaticfasteasy to host

how it works

Private backend.

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.

  1. One WordPress backend

    Headless WordPress holds the content, media, users and roles for every site. Editors and agents work there; visitors never see it.

    headlessone codebase

  2. Build

    When someone publishes, a build pulls that site’s content and turns it into a finished static site.

    only connectionon publish

  3. Independent sites

    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.

    staticcustom per site

connection between backend and sites closed build
  • Nothing to break into

    The live sites have no database and no admin login, and they never talk to the backend.

  • Sites keep running

    Backend down for maintenance? Every site stays online, because each one is already built.

  • One thing to maintain

    Updates, security fixes and new features go into one backend, not one per site.

open for projects

More than one site? Run them all from one WordPress.

Tell me how many sites you run and who edits them. I’ll show you what MultiPress would look like for you.