Skip to content

Multi-site ecosystems

Multiple sites. One system.

We unify sites, languages, and markets into a cloud ecosystem, with centralized administration, API synchronizations, and AI agents connected via MCP.

What you get

A single place to manage all your group’s sites, instead of three or five separate systems with different accounts and content copied manually from one to another. Each site keeps its own domain, identity, and language.

The site you're reading now runs on such a platform.We built it ourselves and use it for our own sites, with the same shared administration and isolation between them that we’re offering you.

What it solves

One central admin hub

Manage all sites in the same dashboard, with permissions based on roles and sites. For example, the team responsible for the Romanian market can see only its relevant content. Common structure or template changes are implemented just once.

Languages and markets

Manage content in multiple languages and identify any translations that are out of date. Links between language versions are set up correctly for search engines, and redirections from old sites are retained.

Sync with your systems

Catalogs, stock, and product lists can be automatically pulled from your internal applications. We validate the source, detect changes, and apply additions, updates, and deletions in a single operation to avoid incomplete data.

Controlled AI agent connectivity

The platform can allow AI assistants to handle content operations directly from apps like ChatGPT or Claude. Access operates via Model Context Protocol, with authentication, individual site permissions, and full action logging.

How it's built

A single admin instance serves all the sites, and each site has its own frontend, domain, and storage space for images and files. A site's content is not visible from the admin of another site.

Pages are built from ready-made blocks that editors assemble themselves, with previews before publishing. A new site can be added without affecting the existing ones.

Technologies: Payload CMS and Next.js, PostgreSQL, S3-compatible storage, Docker and Traefik, Model Context Protocol with OAuth for agent access, plus automated delivery via CI/CD, with separate development, testing, and production environments.

An ecosystem we built: three sites, two countries, one platform

Unified sites
3, from 3 separate systems
Managed languages
3
Content types
35
Page blocks for editors
23
Tools exposed to AI agents
204
Automated tests
349
Development time
13 months
Status
fully technical, in pre-production; public launch per client schedule

Who it's for

For groups with multiple brands, subsidiaries, or markets that currently manage each site in a different system and manually copy content between them. For companies looking to enter a new market without rebuilding the whole platform. For organizations with data in internal apps that want their sites to update automatically.

Who it's not for

If you manage a single site and don't plan to expand to other brands, languages, or markets, a multi-site platform would add complexity without sufficient benefit.

Unification also brings limited advantages when sites don’t share templates, content types, data, or editorial processes. In this case, it may be more efficient to keep them independent.

How much it costs

The cost depends on the number of sites, volume of content to migrate, and required integrations. Usually, most of the effort is spent migrating existing content and preserving URLs and search engine visibility.

The first site is implemented as a distinct project, with its own deliverables and price. After it launches, the next sites can use the platform and already built components, which lowers implementation cost. You'll get a phased estimate before work begins.

Hosting is billed monthly and shared among all sites in the ecosystem.

Billing is in RON, with EUR amounts converted at the BNR exchange rate on the invoicing day. Prices exclude VAT.

How the migration works

Site by site, not all at once.

1. Inventory and architecture

Which sites you have, what content, what languages, what data comes from other systems, and who has what rights. From here, the shared structure emerges and what's left unique to each site.

2. First site

We build the platform and take the first site end to end: templates, migrated content, redirects from old URLs, and training for the publishing team.

3. The other sites

Each new one comes onto the already-built structure, at your pace. Unmigrated ones continue as they were, untouched.

4. Integrations and automations

We connect the data sources and, if you want, open the platform to AI agents for content operations.