7DS CMS is a multi-tenant content platform. One application serves several completely separate client brands — each with its own domain, theme, menus, pages, blog and SEO configuration — with content isolated per tenant at the data layer rather than by convention. Adding a brand is a DNS record and a database row, not a fork and a redeploy.

Multi-tenant: one deployment, many branded sites
Pages, blog, menus, media and SEO all editable without a release
Tenant resolved from the host header — no path prefixes

✅

Delivered for client brands, several of them served from a single deployment.

What it does

Capabilities delivered and running for a client.

Host-based tenancy

The brand is resolved from the incoming domain, so each site is genuinely its own property.

Isolated content

Every content table carries a tenant key, enforced in the repository layer rather than trusted to callers.

Themes as data

Colours, fonts and branding are configuration, so a redesign is not a deployment.

Pages and blog

Rich-text editing with SEO title, description, slug and publish state per entry.

Menu builder

Header and footer navigation composed per tenant without touching templates.

Media library

Uploads on a persistent volume with an in-place picker for any image field.

SEO controls

Per-page metadata, canonical URLs and structured data managed from the admin.

One admin, many sites

Staff switch brands from a single panel instead of juggling logins.

Who it's for

Where this tends to pay for itself.

Agencies running several client sites from one stackGroups with multiple brands under one operationBusinesses tired of paying per-site licence fees

7DS CMS