Development · head-to-head
BrewPage vs Kroki
BrewPage is a free, account-less content host: a POST to endpoints like brewpage.app/api/html turns HTML, Markdown, JSON, key-value pairs, or a whole multi-file site into a short public URL, protected by an anonymous owner token instead of a login. Pages default to a 15-day TTL (30-day max) and can be password-protected, and the project ships both an MCP server (brewpage-mcp on npm) and a Claude Code plugin for programmatic publishing.
Kroki puts a single unified HTTP API in front of two dozen open-source diagram-as-code renderers, including PlantUML, Mermaid, GraphViz, D2, BPMN, Excalidraw, and WaveDrom, so callers send diagram source text and get back an image with no local toolchain to install. A GET request embeds the (deflate+base64-encoded) diagram directly in the URL, making it trivial to drop live diagrams straight into Markdown or HTML. The project and its public instance at kroki.io are free and open source, with self-hosting via Docker documented for anyone who needs a private instance.
| BrewPage | Kroki | |
|---|---|---|
| Authentication | None | None |
| Pricing | free | free |
| Formats | HTML, JSON, Markdown | SVG, PNG, PDF, JPEG |
| CORS | no | yes |
| HTTPS | Yes | Yes |
Kroki supports CORS, while BrewPage doesn't — pick Kroki for direct browser calls.