Pricing
The writing is free and stays free. It runs on your own hardware and the Claude subscription you already pay for, so it costs us nothing to let you do it. You pay only for the two things that genuinely need a server: generating images and hosting them where a client's CMS can reach them.
Free
Everything the engine does on its own, unmetered.
ghPro
Most writersFor anyone publishing to a CMS instead of a repo they control.
Team
For an agency where several writers share the same clients.
Everything in Pro — 100 generated images a day, asset hosting, the CMS wizard — with no renewal. About what sixteen months of Pro costs.
Line by line
Every row below is a thing the engine already does. The only difference between plans is whether it calls your machine or our server to do it.
| Feature | Free | Pro | Team |
|---|---|---|---|
| Writing | |||
| Posts per monthDrafted, gated and published | Unlimited | Unlimited | Unlimited |
| The full pipelineStructure, AI-tell lint, humanize, readability, interlink | |||
| Runs on your Claude subscriptionNo API key, no per-word charge from us | |||
| Pictures | |||
| DiagramsRendered as SVG on your machine, in your theme | Unlimited | Unlimited | Unlimited |
| Generated imagesThrough our proxy — no provider account needed | — | 100 / day | 500 / day |
| Your own provider keyOpenRouter or Gemini, billed to you | |||
| Public asset hostingSo a CMS post doesn't arrive with broken images | — | ||
| Publishing | |||
| Git — branch, commit, pull requestUses the git and gh auth already in your terminal | |||
| CMS wizardWordPress, Ghost, Webflow, Sanity | — | ||
| Shared CMS connectionsWhich platform, which endpoint, mapped to which fields | — | — | |
| Per-writer tokensRevoke one writer without rotating everyone | — | — | |
| Where things live | |||
| Drafts and postsThe files themselves | Your machine | Your machine | Your machine |
| CMS credentialsTokens that can write to a client's live site | Your machine | Your machine | Your machine |
Questions people actually ask
There isn't one. The model runs on the Claude Code you are already signed into, on your own hardware. Letting you draft a post costs us nothing, so charging for it would be charging for the privilege of using your own subscription.
No, and not as a policy — as an architecture. The engine runs on localhost
and this site is static HTML. There is no endpoint that receives a draft.
The two paid features are the exceptions, and only for what they need: the image proxy receives a prompt, and asset hosting receives a picture you chose to publish.
Not on Pro or Team — that's most of what you're paying for. On Free you can still generate images by supplying your own OpenRouter or Gemini key, billed to you directly.
Nothing. They are files in your own repo and were never anywhere else. You lose image generation and hosting; every post you already published stays exactly where it is.
Images already hosted keep their URLs — they're content-addressed and immutable.
The lifetime of blogwriter, not yours — if the project stops, the hosted parts stop with it. What does not stop is the engine: it runs on your machine, it is in the repo, and the paid pieces can be self-hosted with your own keys.
Your posts are unaffected either way. They are files in your own repo.
No. $49 covers the whole team, with a pooled daily image budget and one token per writer so you can revoke someone without rotating everybody else's.
Yes. The image proxy and asset store are two files in the repo, and they read
OPENROUTER_API_KEY, BW_TEAM_TOKENS and BW_DAILY_CAP
from your own environment. Paying us is the convenience, not the permission.
Install the engine, run blogwriter serve, and open the app.