Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchYou can manage multiple websites through one CMS dashboard, but “multisite” can mean anything from shared content in one installation to fully separate projects in a common interface. In a September 2026 account, Plovant’s creator, Shokichi Uehara, describes consolidating seven apps into one hostname-routed delivery app while operating more than 10 websites. It is a useful example of the model—and of the migration risks—not independent proof that every team should consolidate.
How Plovant’s one-dashboard approach works
Uehara describes Plovant as a multi-tenant CMS built to operate more than 10 websites from one repository and management console. According to his account, the system routes a site based on the hostname a visitor accesses, then delivers the sites through one app. The team had previously consolidated seven apps into one; under the old setup, Uehara says, pushing to the main branch redeployed seven sites together.
As an Amazon Associate I earn from qualifying purchases.
The claimed product capabilities are also author-reported: block-based editing; AI-assisted page, image, and logo generation; block-level multilingual translation; and a SaaS control plane for organizations, teams, permissions, API keys, and domains. Uehara says reusable blocks include text, images, and forms, and that common packages for block definitions, editing, and delivery are shared across products. Premium sections and templates are assembled from those blocks. These descriptions come from the author’s account, not independent product testing. Read Uehara’s September 25, 2026 account.
One dashboard does not necessarily mean every site shares the same content, permissions, deployment path, or failure domain. The hostname-routing design is a particular implementation choice: it puts site selection at the delivery layer while consolidating applications and management. That can reduce duplicated app maintenance, but a shared app also makes release behavior and recovery planning important.
What consolidation involved in the reported case
The project figures are specific to Uehara’s account, not industry benchmarks: more than 10 websites, seven apps consolidated into one, and five unused sites removed. The transition was not disruption-free. During domain migration, one site was temporarily taken down; leftover delivery settings also needed attention. Those details make the case useful for planning, rather than evidence that a single dashboard automatically prevents outages or lowers total cost.
Plan the cutover, not just the content move
- Inventory active sites, domains, delivery settings, assets, and integrations before moving anything; identify obsolete sites and configuration separately.
- Decide how hostnames map to sites and test each domain against the intended content before changing public DNS or routing.
- Define what a rollback looks like if a domain cutover fails, including who can restore the previous destination and how quickly.
- Check whether publishing or deploying one site triggers work for others. The reported old setup redeployed seven sites together on a main-branch push; another system may behave differently.
What “multisite” and “multi-tenant” mean in practice
These terms do not describe one universal architecture. A platform may host multiple sites inside one CMS instance, or offer a shared interface that manages isolated projects. Those choices affect what teams can share, who can access it, and how releases are coordinated.
| Platform or model | Documented structure | Important consideration |
|---|---|---|
| Plovant, as described by its author | One repository and management console; hostname-based routing into one delivery app. | Author-reported design and operating experience, not independently verified. |
| Sitefinity | Its documentation describes multiple sites in one CMS instance, with options for different languages, site-specific permissions, and shared content. | Some modules are common across sites, and release cycles should be synchronized. Sitefinity documentation. |
| Optimizely CMS | A search-indexed documentation summary describes sites sharing a server file structure, database, and code base, with a license-defined site limit. | The documentation page redirected during access, so treat this as a summary rather than a freshly verified specification. Confirm current licensing and architecture with Optimizely. Optimizely CMS documentation. |
| Storyblok | Its product page describes managing sites, apps, and projects in one interface while assigning separate projects to “spaces.” Each space has its own repository, components, assets, environments, domains, collaborators, and permissions. | Separate spaces offer a different isolation model from sharing one CMS instance. Storyblok’s multi-tenant CMS overview. |
| Concrete CMS | It also presents a multisite offering with centralized management. | This is a category example, not a comparative evaluation. Concrete CMS multisite. |
How to choose a CMS for multiple websites
Compare the way a platform handles boundaries and operations, not just how many sites appear in its dashboard. The right arrangement depends on whether sites belong to one organization, separate clients, or different teams with independent release needs.
Recommended Free Tools
- Isolation: Can each site have separate content, assets, environments, and collaborators, or are these shared within one instance?
- Permissions: Can roles be scoped to a site, project, or content type? Is access granular enough for client teams and contractors?
- Domains and recovery: How are domains connected, and what is the documented recovery path if a cutover points to the wrong site?
- Languages: Are translations managed at site level, content level, or block level? Confirm how the workflow handles updates to source content.
- Release coupling: Does a shared code base or common module mean sites must move together? Sitefinity specifically warns that some modules are common and release cycles should be synchronized.
- Build and deployment behavior: Does a change to one site rebuild or redeploy others? Ask for the actual behavior of the edition and hosting arrangement you would use.
- Limits and migration: Verify licensed site limits, the process for moving existing domains and content, and whether projects can later be separated.
Keep client analytics separate from CMS management
A CMS dashboard and an analytics dashboard solve different problems. Plausible’s agency documentation describes consolidated views across client sites, client sharing and access options, and ownership transfer. Its documentation, updated August 19, 2026, says standard plans include up to ten sites and describes Enterprise allowances; those plan details can change, so verify current terms before relying on them. Plausible is an analytics layer, not a CMS feature. Plausible’s agency documentation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
