ProsewireRun locally
Apache-2.0 Publishing infrastructure you can own

Own your publishing.
Keep your website.

Prosewire gives editors a focused publishing workspace and gives developers several ways to bring the same content into an existing site.

Self-hostable · portable exports · no iframe

prosewire / fieldnotesPublish ↗

DRAFT · 6 MIN READ

Your content should outlive your website stack.

Portable publishing starts with a clean source of truth and ends with a reading experience that feels entirely your own.

One story, every surface

Write once, then deliver semantic HTML, structured JSON, or a native SDK response wherever your readers already are.

ONE SYSTEM, FROM DRAFT TO DELIVERY

Editorial control without a frontend rebuild.

Writers get a dedicated publishing workflow. Developers choose how published content reaches the site and keep control of the surrounding experience.
01

Editorial control

Draft, schedule, publish, revise, localize, organize, and archive from one focused workspace.

02

Discovery foundations

Canonical URLs, automatic redirects, metadata, JSON-LD, RSS, sitemaps, authors, and content checks.

03

Flexible delivery

Use an embed, rendered HTML, public JSON, or the typed SDK. No iframe and no forced frontend.

04

Controlled automation

Scoped keys, the management API, CLI, and MCP tools keep read, write, and destructive operations explicit.

Embed first.
Build custom when you need to.

Start with one script, then move to rendered HTML, public JSON, or the typed SDK without migrating content to another system.

Compare integrations
EmbedTypeScriptHTTP
<div data-prosewire="fieldnotes"></div>
<script
  async
  src="https://publish.example.com/embed.js"
  data-blog="fieldnotes"
></script>
ConnectedSemantic HTML · no iframe

PORTABLE BY DESIGN

Your content. Your database. Your exit plan.

Run the complete stack yourself and export posts, authors, categories, redirects, and metadata whenever you need them.Self-hosting guide

EXPLICIT AUTOMATION BOUNDARIES

Automate publishing without hiding the risk.

Publication-scoped keys, audit history, and declared read, write, and destructive operations keep API, CLI, and MCP workflows understandable.See the architecture

OPEN SOURCE PUBLISHING INFRASTRUCTURE

Bring publishing
into your stack.