Multi-site workspaces

Give every site its own operating context.

Keep sources, vectors, brand rules, content, Search Console evidence, permissions, and destinations separated by site.

View on GitHub Self-host BlogFactory

Site isolation · Shared account · Explicit active workspace

Content control loop

Illustrative product schematic

BlogFactory · Editorial control schematics

Evidence enters. A reviewed CMS draft leaves.

Ready

Sources

RSS · briefs · search

Scoped

MCP agent

Research · create · revise

Working

BlogFactory draft

Versioned work

Required

Human review

Preflight · destination

Draft only

CMS draft

Never live publish

Evidence readRevision trackedApproval explicitDelivery idempotent

Why BlogFactory

Operate a portfolio without mixing the work.

Separate context

Each domain keeps its own pages, topics, and knowledge.

Switch explicitly

The active site is visible before an operator or agent acts.

Refresh deliberately

Rebuild page context and topics for the selected domain.

Scale the account

Manage multiple connected sites from one control surface.

Workspace proof

Three sites, three separate operating contexts.

The Sites surface makes the active domain, page context, topics, and management actions explicit.

Connected-domain inventory
Current-site marker
Page and vector context

BlogFactory multi-site workspace listing connected domains and their site context — Product capture · August 23, 2026. Values shown belong to the captured workspace.

How it works

Create, enrich, and activate a site.

Add a domain

Create the site boundary in the authenticated account.

Build context

Refresh pages, vectors, and topics for that domain.

Use the workspace

Connect sources, agents, search, and destinations to the active site.

Capabilities and boundaries

Built for controlled content operations.

Site boundary

All core product contracts are tenant and site scoped.

Sources and content
Brand and writer context
Search property
CMS destinations

FAQ

Before you connect.

Does BlogFactory keep sites separate?

Yes. Content, sources, permissions, provider access, search properties, and destinations remain scoped to the authorized site.

Can an MCP agent publish live or delete content?

No. Agent authority stops at approved CMS draft creation. Live publishing, deletion, credentials, and account administration stay outside MCP.

Can I self-host BlogFactory now?

Yes. The public repository is available for self-hosting as a release candidate. BlogFactory Cloud is not available yet.

Run BlogFactory where your content operation lives.

Inspect the public source, then follow the source-build Docker Compose guide for the open-source release candidate.