Prosewire gives your team an editor, publishing workflows, and clean content APIs. You keep the frontend, the database, and every exit.
Saved a moment ago
Engineering
A canonical content store lets your team change frameworks without rebuilding years of editorial work.
One publishing system
Editors get a focused workspace. Developers get predictable output. Both work from the same content model.
Add semantic HTML, a small script, the raw API, or the typed SDK. Prosewire does not put your blog in an iframe.
Every post includes clean URLs, metadata, JSON-LD, RSS, sitemaps, author pages, and writing-side SEO checks.
Draft, schedule, review, localize, pin, revise, redirect, and restore content without asking a developer.
Self-host the full stack and export posts, authors, categories, redirects, and metadata in documented formats.
Permissions, audit history, APIs, and staging-friendly configuration all ship under the Apache 2.0 license.
The REST API, TypeScript SDK, CLI, and MCP server share one contract with the dashboard and public reader.
Quick start
Point the scaffolder at a Prosewire deployment. It detects Next.js or Astro and adds thin native routes for your blog.
Read the setup guide$ pnpm create prosewire@latest \
--url https://your-prosewire-deployment \
--blog fieldnotes \
--route /blog
# Next.js or Astro routes are ready to style.
Your content, your rules
Run Prosewire on your own infrastructure, connect the frontend you want, and export the complete publication whenever you need it.