BlogFactory

BlogFactory

The draft-only agent control plane for multi-site content operations.
Give agents useful authority through MCP. Keep people in control of review, approval, and CMS delivery.

Website · Self-host · MCP guide · Cloud billing · Release plan · AGPL-3.0-only

[Deploy on RepoCloud]

Self-hosted Bring your own AI Site-scoped access Never publishes live

[BlogFactory turns source signals into reviewed CMS drafts while keeping live publishing locked]

A calmer content operation

BlogFactory keeps the operating context around AI-assisted content work in one place: source evidence, drafts, revisions, SEO metadata, review, preflight, delivery destination, and a sanitized operation record.

source evidence  → agent work or caller-authored draft  → revision + SEO metadata  → human review + preflight  → selected CMS destination as a draft

Agents do the work through MCP. The web app is where operators see what needs attention, resolve blockers, review the current version, and approve a CMS handoff. The server-enforced authority ceiling is intentionally narrow: no live publishing, deletes, credential access, arbitrary providers, or admin tools through MCP.

[BlogFactory brings sources, review, growth, and CMS draft delivery into one control plane]

Product captures

[BlogFactory Search Growth with complete-day provenance and next actions]

Search Growth turns evidence into reviewed action

Connect Search Console context, distinguish complete from preliminary data, rank work, plan it by date, and create a draft only when an operator is ready. Observation windows are shown as correlated signals, never as ranking guarantees.

[BlogFactory MCP Connections with site-scoped authorization]

MCP has useful authority and hard boundaries

Each connection is site-scoped. Clients discover the active catalog from the server, while provider credentials stay outside the agent conversation. The Review Card brings current revision context, warnings, destination selection, and explicit draft confirmation into compatible MCP clients.

_{Product captures from blogfactory.io. Values belong to the captured workspace; the tool catalog is discovered live.}

What ships in v0.1.0

Self-host BlogFactory for free. BlogFactory Cloud is the managed service operated from the private BlogFactoryHQ/blogfactory-cloud repository; its pricing, subscriptions, checkout, and entitlement code is not part of this open-source core and never gates self-hosted instances. Read the release plan for the distribution roadmap.

Companion projects

Explore both projects in the Free & Open Source Tools hub.

Both projects work independently. They can supply or deliver content around BlogFactory, but they do not broaden BlogFactory's server-enforced draft-only authority.

Start locally

BlogFactory uses npm workspaces: a React/Vite web app and a Hono/TypeScript API, backed by PostgreSQL and S3-compatible storage.

git clone https://github.com/BlogFactoryHQ/blogfactory.gitcd blogfactorynpm installcp .env.example .envnpm run db:migratenpm run dev

The web app runs on http://localhost:8080 and the API on http://localhost:3000. Add only the credentials required for the flow you are testing; never point PostgreSQL integration tests at a shared production database.

Self-host with Docker

git clone https://github.com/BlogFactoryHQ/blogfactory.gitcd blogfactorycp .env.self-host.example .env# Fill every required value and set ADMIN_EMAILS.docker compose build --pull api webdocker compose up -d

The verified topology includes the web app, API, PostgreSQL, MinIO, migrations, persistent volumes, and the bounded scheduler. Follow the full self-hosting guide before exposing an instance to the internet.

Hosted production

The managed service uses Cloudflare in front of an immutable Docker Compose deployment on Hetzner in Nuremberg. PostgreSQL 18, the Bun/Hono API, the persistent worker, the backup scheduler, and the web app run in that stack; private EU Cloudflare R2 stores images and age-encrypted database backups. GitHub Actions builds immutable images in GHCR; Vercel retains the last clean deployment as a DNS rollback target rather than serving current production traffic.

This hosted topology and the Cloud-only billing/authentication overlay are maintained in the private BlogFactoryHQ/blogfactory-cloud repository. Shared product changes originate in this public core and sync one way into Cloud; the hosted topology does not change the community self-host contract above.

How the system is shaped

operators ── <instance-origin> ─────┐                                    ├─ shared tenant-scoped services ─ PostgreSQL + S3-compatible storageagents ───── <instance-origin>/mcp ─┘                                   └─ CMS drafts / Search Console / configured AI providers

Web and MCP are transports over the same services. Queue classification, revision rules, review preflight, Search Console reads, permissions, and CMS draft delivery are not duplicated in the UI or agent tools.

Documentation

• Architecture and service ownership
• MCP, OAuth, tool catalog, and Review Card
• Operations, deployment, and production acceptance
• Cloud billing, entitlements, and Managed AI
• Self-hosting with Docker Compose
• Release plan and Cloud boundaries
• Documentation index
• Contributing

Development checks

npm run typechecknpm run lint --workspace=webnpm run test --workspace=webnpm run test:servernpm run buildgit diff --check

Database, tenancy, ledger, and shared control-plane changes also require npm run test:postgres against a disposable database.

BlogFactory is licensed under AGPL-3.0-only.