Ready
Open source · Self-hosted · MCP-native
Run your content operation on infrastructure you control.
Connect sources and AI agents to one site-scoped workflow for research, revision, human approval, and CMS draft delivery. Live publishing stays outside the agent boundary.
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
Product overview
Keep every draft and decision in one workspace.
The content inventory keeps source, writer profile, model, lifecycle state, and SEO readiness attached to the work.
- Search and filter the inventory
- Open the current revision
- Keep readiness visible
MCP instrument panel
Let agents work inside a visible authority boundary.
Operators can connect an MCP client to one site, discover the current catalog live, and keep credentials outside agent reach.
Human approval
Agents can work. Humans stay in control.
Review provenance, revisions, SEO readiness, destination, and preflight before an approved article becomes a CMS draft.
Review workspace
Illustrative product schematicBlogFactory · Editorial control schematics
One queue for blockers, revisions, and approval.
Review Queue3 require action
Snippet refreshRevision readyReview
Evergreen guideSEO field missingBlocker
Weekly briefDestination confirmedApprove
Preflight
Ready for CMS draft
- ✓ Revision current
- ✓ Destination selected
- ✓ SEO fields complete
Ghost · Primary publicationApprove draft delivery
Grow
Move from Search Console evidence to reviewed action.
Search Growth connects complete-day provenance, ranked opportunities, dated work, and the same editorial approval path.
- Complete-day data boundary
- Ranked next action
- No ranking guarantee
The product system
Operate, grow, control, and deliver without losing the thread.
01
Operate
Plan, create, review, and monitor content work.
4 focused capabilities →02Grow
Turn complete-day search evidence into reviewed action.
5 focused capabilities →03Control
Keep agents, sites, voice, providers, and spend in bounds.
5 focused capabilities →04Deliver
Connect the stack and hand off an approved CMS draft.
2 focused capabilities →Install from source
Clone, configure, build, and run it on your infrastructure.
Release candidate
Community self-hosted
Versioned GHCR images are not published yet. Build the web and API images from the public repository.
Read the self-host guidegit clone https://github.com/BlogFactoryHQ/blogfactory.git
cd blogfactory
cp .env.self-host.example .env
docker compose build --pull api web
docker compose up -dProduct boundaries
Control stays with your team.
Bring your own AI
Your model credentials and provider choice stay under your control.
Site-scoped access
Every connection and operation is limited to the sites you authorize.
Draft-only delivery
CMS handoffs create drafts for human review. BlogFactory does not publish live.
FAQ
Before you self-host.
Who is BlogFactory for?
Publishers and content teams operating one or more sites and coordinating repeatable editorial work.
Does BlogFactory include an AI model?
No. You connect the AI provider you already use and keep control of that relationship.
Can it publish directly to a live site?
No. The highest delivery authority is creating a CMS draft after explicit approval.
What can agents do?
Agents can research, generate, revise, diagnose, and prepare CMS drafts through BlogFactory's site-scoped MCP tools.
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.
Self-host the operation. Keep editorial control.
Start with the open-source release candidate. BlogFactory Cloud is coming soon.