Apache-2.0Publishing infrastructure you can own

Add a production blog to Next.js or Astro in about five minutes.

Run one command to add native blog routes. Prosewire handles the editorial workspace, scheduling, metadata, feeds, and content APIs.

Add Prosewire to your site View the live demo

pnpm create prosewire@latest

Run locally View on GitHubSelf-hosted or Cloud

Run the scaffolder

Point it at a Prosewire deployment and choose the native route.

pnpm create prosewire@latest \
  --url https://publish.example.com \
  --blog fieldnotes \
  --route /blog

Review the written routes

The command refuses to overwrite a route that already exists.

Start your app

Style the semantic pw-* hooks or replace the typed components.

Routes written

app/blog/page.tsxapp/blog/[slug]/page.tsxlib/prosewire.ts

Dependency added

@prosewire/next

Done

Your blog now renders inside the site you already have.

Native page preview

localhost:3000/blog/shipyard-notes

May 24, 2026 · Shipyard notes

Shipyard Notes

Botanical leaves in a vintage ink illustration

A quiet morning in the shipyard. Notes on small details, materials, and what lasts.

Run the same command

The scaffolder detects Astro and adds the matching integration package.

pnpm create prosewire@latest \
  --url https://publish.example.com \
  --blog fieldnotes \
  --route /blog

Choose static or server rendering

Static projects fetch content at build time. Server projects resolve it per request.

Keep your layouts

Use injected routes for speed or compose the exported Astro components yourself.

Integration added

astro.config.mjs@prosewire/astro

Routes injected

GET /blogGET /blog/[slug]

Done

Native Astro pages, with no bundled stylesheet or client runtime.

Native page preview

localhost:4321/blog/shipyard-notes

May 24, 2026 · Shipyard notes

Shipyard Notes

The same content, rendered by Astro and styled by your site.

Use the generated routes or keep the small typed setup in your own codebase.

Read the integration guide

Next.js

import { createProsewireApp } from "@prosewire/next/app";

export const blog = createProsewireApp({
  baseUrl: "https://publish.example.com",
  publication: "fieldnotes",
  basePath: "/blog",
});

Astro

import prosewire from "@prosewire/astro";

export default defineConfig({
  integrations: [
    prosewire({
      baseUrl: "https://publish.example.com",
      publication: "fieldnotes",
      basePath: "/blog",
    }),
  ],
});

Self-host the complete stack

Your infrastructure, your Postgres, your backups.

The repository includes web, worker, migration, Postgres, and Redis services. Use an immutable tag or commit for production.

Open the Docker Compose guide

git clone https://github.com/prosewire/prosewire.git
cd prosewire
cp .env.example .env

# Replace the local-only credentials, then:
docker compose up -d --build
docker compose ps

import { createPublicClient } from "@prosewire/sdk";

const content = createPublicClient({
  baseUrl: "https://publish.example.com",
  blog: "fieldnotes",
});

const posts = await content.listPosts({
  page: 1,
  pageSize: 10,
});

Published content

{
  "items": [
    {
      "title": "Shipyard Notes",
      "slug": "shipyard-notes",
      "status": "published"
    }
  ],
  "page": 1,
  "pageSize": 10
}

Compare every delivery option

Need help? Read the complete integration guide

From one command to a published blog.

Connect

Point the scaffolder at your Prosewire deployment and publication.

Generate

Add native routes and a small typed configuration to your project.

Publish

Write in Prosewire, then render the result inside your existing site.

The old approach

Blogs bolted on with an iframe or rented CMS.

The blog looks and behaves like a separate website.
Content becomes harder to export or move.
Editorial history lives behind someone else's terms.

The Prosewire approach

Native pages, portable content, and infrastructure you control.

Blog routes remain first-class pages in your app.
Postgres and versioned exports keep the content portable.
Revision snapshots retain actor and version data.

Built for editors and developers

Publishing that fits the product you already have.

A focused editorial workspace

Draft, schedule, publish, localize, and organize posts without turning your application into a CMS dashboard.

Explore the workflow

Your content stays in Postgres

Back up the database yourself and export posts, authors, categories, redirects, metadata, and revision snapshots.

Read about exports

Every destructive edit leaves a record

Prosewire stores versioned revision snapshots with actor data before destructive content changes.

See content history

Native delivery by default

Use framework routes, semantic HTML, public JSON, or the typed SDK. Prosewire does not force an iframe or a frontend.

Open the API reference

Self-hosted, always available

Run the full publishing stack in your environment.

Build from the open repository, keep Postgres on infrastructure you trust, and define your own backup and retention policy.

Docker Compose topology documented
Postgres for durable content storage
Redis-backed worker for scheduled work
Versioned JSON and CSV exports

Read the self-hosting guide

docker-compose.yml

services:
  postgres:
    image: postgres:17-alpine
    volumes:
      - prosewire_postgres:/var/lib/postgresql/data

  redis:
    image: redis:7-alpine
    command: [redis-server, --appendonly, "yes"]

  migrate:
    build: .
    command: [node, apps/worker/dist/migrate.mjs]

  web:
    build: .
    ports: ["3000:3000"]

  worker:
    build: .
    command: [node, apps/worker/dist/index.mjs]

Open repository

Read the code, pin a commit, and operate the same stack yourself.

Open GitHub

Portable exports

Export publication relationships, revision snapshots, and post fields.

Read about exports

Postgres first

Your deployment owns the database, backups, encryption, and retention policy.

Review operations

Questions before you start

Frequently asked questions

Is Prosewire really open source?

Yes. The repository is available under the Apache-2.0 license, including the dashboard, APIs, reader, SDK, CLI, and MCP server.

Will it work with my existing Next.js or Astro site?

Yes. The scaffolder detects Next.js App Router, Next.js Pages Router, or Astro and writes thin native routes without overwriting an existing route.

Does Prosewire ship frontend styles?

No. The framework packages render semantic pw-* markup without a bundled stylesheet or client runtime, so the blog can use your design system.

Can I move my content later?

Yes. Versioned JSON exports include publication relationships and revision snapshots, while CSV covers posts and related identifiers.

What does self-hosting require?

The complete stack runs the web app, a worker, one-shot migrations, Postgres, and Redis. The Docker Compose guide covers the topology and production checks.

Is there a managed option?

Yes. Prosewire Cloud runs the platform for you, while the self-hosted project remains available when you need full infrastructure control.

Ship your blog. Keep your content.

Add Prosewire to your site Open Prosewire Cloud

Open source · Apache-2.0 · Self-hosted or Cloud