CatchCMS is a multi-site CMS for business websites. One system instance can manage separate brand websites, business units or client projects. Each incoming domain resolves to its site, whose content, languages and domain-bound theme are then used to render the page. It fits businesses managing several websites and developers delivering multiple website projects.
How do you manage several websites in one admin?
Administrators select a target site before maintaining its categories, content models, products and articles, forms and site settings. These records are saved and read within that site's scope. Each brand can have its own content structure and a suitable theme assigned to its domain, with a separate content management and presentation scope.
Multi-site here means business data isolation inside one system. Separate deployments, databases and independent client operations should be planned according to delivery requirements. Cross-site product synchronization, centralized distribution and shared approval workflows are project extensions to plan separately.
Configuration steps from a new site to a public website
- Prepare the site inventory: list each website's name, domain, owner, languages and page types, and define its maintenance scope.
- Create and enable the site: a super administrator sets the site, supported languages and default language in site management. Assigned sites determine a regular administrator's management scope.
- Bind a domain and theme: enter the domain and choose its theme in domain management. A domain can serve the site's languages or be bound to one enabled language. Deployment staff configure DNS, server domain routing and HTTPS.
- Build categories and content: select the correct site, configure models and categories, enter products, case studies, articles and contact details, and check how the theme renders the fields.
- Assign accounts and verify: the super administrator assigns manageable sites and functional permissions to team members. Visit each real domain and check site identity, pages, language, theme and forms.
An example with two brand websites
This is a fictional example. Brand A uses a.example.com for equipment and technical documents. Brand B uses b.example.com for service offerings and case studies. The team creates two sites in one instance, configures their categories and domain themes separately, and assigns A's operator to site A.
For acceptance testing, create a test product in site A and verify its category and detail pages on A's domain. Open the corresponding pages on B's domain and confirm that B's business content remains in place. Use A's operator account to check the available sites and record scope, then complete a real content update and form submission check.
How does MCP keep AI operations within a target site?
An MCP token is tied to an admin account. Site-level operations specify a site_id, and the server checks both functional permissions and site assignments. Changes to account site assignments apply to existing tokens. Teams can issue tokens for different owners and manage access through expiry and revocation.
A content update can follow this sequence: read the target site, read its model and fields, update the specified record, read it back, and inspect the public page. State the site, records and allowed fields in the task. The relevant owner confirms product facts and publishing scope. See the MCP content update tutorial.
Questions to confirm before purchase
Can sites use different themes and languages?
Sites can bind their own languages, and domains bind the corresponding themes. Configure and verify language entries and theme output for each site. See multilingual CMS support.
How many sites does a license include?
Confirm technical capability and commercial licensing separately. Review pricing and licensing and ask the product team about site count, domains, deployment scope and use for internal projects or client delivery.
Can clients maintain their own content in one admin?
Assign sites to admin accounts and use role permissions to define available operations. Independent databases, deployments and shared cross-site workflows require project-specific arrangements.
Explore the frontend demonstration website, then contact the product team to confirm deployment documentation, account responsibilities and licensing. Use the enterprise website CMS selection guide to organize your evaluation.
Plan the next step for your project
Review source-code plans and updates, then use project enquiries to confirm site counts, languages, deployment and client-delivery needs.