Bring your own AI

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.

Encrypted provider keys · Model choice · Provider attribution

Provider control
Illustrative product schematic

BlogFactory · Editorial control schematics

Models connect without exposing provider keys.

Site vault

Encrypted

Agent access: none
01OpenRouterConnected
02OpenAIConnected
03GoogleConnected
04UsageAttributed
Choose the modelSee provider costKeep provider control

Why BlogFactory

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.

Provider proof

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
BlogFactory provider balance, request, image, and daily token usage analytics
Product capture · August 23, 2026. Values shown belong to the captured workspace.

How it works

Connect, select, and operate.

01

Add provider access

Store a supported credential in the authenticated control surface.

02

Choose the model

Select an available model for the relevant workflow.

03

Run the controlled loop

Create drafts while review and CMS authority stay unchanged.

Capabilities and boundaries

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

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.