Use your models. Keep provider choice under your control.
Connect supported provider access, choose models for the workflow, and keep keys encrypted inside BlogFactory rather than inside agent prompts.
Provider control
Illustrative product schematicBlogFactory · Editorial control schematics
Models connect without exposing provider keys.
Choose the modelSee provider costKeep provider control
Own the model layer without rebuilding the workflow.
Keep provider choice
Select supported text and image models for the work.
Keep keys out of prompts
Credentials are encrypted and never exposed through MCP or logs.
See provider attribution
Usage retains provider and model context.
Keep the same review path
Draft and approval boundaries do not change when the model does.
Model use remains attributable.
Provider balance, requests, failures, image counts, latency, and daily token usage keep model operations visible without exposing the credential.
- Provider balance
- Request and failure counts
- Daily token usage
Connect, select, and operate.
Add provider access
Store a supported credential in the authenticated control surface.
Choose the model
Select an available model for the relevant workflow.
Run the controlled loop
Create drafts while review and CMS authority stay unchanged.
Built for controlled content operations.
Provider control
The operator chooses supported provider access and model.
- OpenRouter
- OpenAI-backed services
- Google-connected services
- Provider-attributed usage
Secret boundary
Keys stay inside the authenticated application boundary.
- Encrypted at rest
- Never returned through MCP
- Excluded from operation history
- No bundled-credit claim
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.