Ready
Give every site its own operating context.
Keep sources, vectors, brand rules, content, Search Console evidence, permissions, and destinations separated by site.
Content control loop
Illustrative product schematicBlogFactory · Editorial control schematics
Evidence enters. A reviewed CMS draft leaves.
Scoped
MCP agent
Research · create · reviseWorking
BlogFactory draft
Versioned workRequired
Human review
Preflight · destinationDraft only
CMS draft
Never live publishEvidence readRevision trackedApproval explicitDelivery idempotent
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.
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
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.
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
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.
How can I use BlogFactory?
Self-host the AGPL-3.0-only release candidate for free, or create a managed BlogFactory Cloud account from $5 per month. Both editions keep CMS delivery draft-only.
Run BlogFactory where your content operation lives.
Inspect the public source, then follow the source-build Compose guide — or let Cloud run it from $5 a month. The boundary is identical in both.