Documentation

Production guidance, from first issue to dispatch.

PubOps keeps planning, assembly, review, readiness, dispatch, and learning in one issue-centered editorial workspace.

Request access ·Back to home

Sections

Where to start

What is PubOps

The product in one paragraph.

Concepts

Publication, track, issue, sponsor placement, dispatch.

API reference

Selected REST endpoints, with authentication and signature requirements.

Self-hosting

Run a durable single-node deployment with SQLite, backups, and health checks.

API

Selected endpoints

Supported PubOps API endpoints
Method	Path	Access	Description
POST	/api/issues/[id]/dispatch	Operator	Dispatch an authorized issue through the guarded publish coordinator
POST	/api/dispatch/[logId]/retry	Operator	Retry an authorized failed dispatch
POST	/api/webhooks/resend	Signed webhook	Receive signature-verified Resend delivery events
GET	/api/library/issue/[id]/post-mortem	Operator	Get an authorized sent-issue post-mortem
GET	/api/metrics	Admin	Read the gated internal counter snapshot
GET	/api/og/[slug]	Public	Render an image for an existing sent issue

Browser mutations require an authenticated operator and same-origin request. Public endpoints use explicit signed-token, webhook-signature, or sent-content contracts.

A deliberate single-node deployment

PubOps supports multiple isolated publication workspaces in one deployment. The supported production topology is a single application replica with the included container, persistent SQLite storage, encrypted backups, readiness probes, and the production preflight—not an unimplemented external database adapter.

Open the operator guides