PubOps help
Start with one issue.
Open the prepared draft and make it yours. No provider setup is needed to write or review.
Help with the next task
One issue. Five views of the work.
Each edition is an issue. These views keep you on the same draft.
Overview
Progress and the next action.
Edit
Write and arrange sections.
Review
Feedback and editorial decisions.
Preview
Saved email and plain text.
Send plan
Audience, destinations, and sending.
What makes an issue ready to send?
PubOps checks sponsor approval, voice, sources, links, and editorial review. Missing evidence stays visible as a blocker. An issue deadline is separate from its send schedule.
What needs a connected service?
- Sending and publishing
- Email needs a configured provider and eligible subscribers. PubOps also has a native web archive. Substack uses a manual export, which never counts as a live send.
- Assistance and payments
- AI suggestions use a configured provider or limited local fallback; you review the changes. Paid subscriptions require configured Stripe billing.
For developers and service operators
Selected endpoints
This is an overview of application routes, not a complete API contract. Operator routes require an authenticated session and the relevant publication permission; browser changes also require a same-origin request.
| Method | Path | Access | Purpose |
|---|---|---|---|
| POST | /api/issues/[id]/publish | Operator | Send an authorized, confirmed issue and destination plan |
| POST | /api/dispatch/[logId]/retry | Operator | Retry an eligible failed destination after readiness checks |
| POST | /api/webhooks/resend | Signed webhook | Receive signature-verified Resend events |
| GET | /api/library/issue/[id]/post-mortem | Operator | Read an authorized sent-issue retrospective |
| GET | /api/og/[slug] | Public | Render an image for an eligible sent issue |
Public routes validate their own access: signed webhooks, scoped links, or published-issue evidence. An uncertain provider outcome must be reconciled before retrying a send.
Self-hosting and first-owner setup
PubOps supports multiple isolated publication workspaces in one deployment. The supported topology is one application replica with durable SQLite and artifact storage. Running it also requires provider configuration, backups, health checks, and deployment verification.
On a new deployment, the setup page uses an administrator-provided setup code to create the first owner, publication, and issue. It is not the registration page for an existing service.
Use the repository’s production deployment and backup runbooks before opening the service to users. A local test does not verify live email delivery, billing, or recovery from a production backup.