Content API
REST for publications, posts, pages, tags, and users. Scoped credentials. Consistent pagination. Markdown rendered to HTML and plaintext on write.
Features
One stack for the publishing loop.
Content API. Postgres. Static Astro themes. Reader plumbing that usually means three vendors. Labels below mark what is production-ready versus scoped per pilot.
Publish and operate
Astro static sites
Publications build to plain HTML and assets. Readers get a fast site without a database hit or client framework on every view.
Scheduling and revisions
Schedule future content. Keep a version trail. Promotion and static rebuilds sit on one guarded path.
Postgres full-text search
Indexed relevance search over published content. No second search product. No second source of truth.
Multi-publication
One service. Separate domains, themes, tags, content, and members per publication.
Scoped access
Publication-bound API keys and read-only build keys. Credentials match the domain and the job.
Ghost archive import
SQLite or JSON. Transactional. Idempotent. Count and URL checks before cutover.
Standard stack
Node.js, Postgres, Astro, Caddy. Inspectable. Portable. Ordinary infrastructure tooling.
Audience capabilities
Memberships and paid access
Free and paid member state, Stripe-backed subscriptions, server-enforced teasers. Fit reviewed per publication.
Subscriber lifecycle and newsletters
Double opt-in, unsubscribe, tracking, issue rendering, send-queue foundations. Sender setup scoped before any pilot promises mail.
Private beta
Bring the publication you want to own.
One email. We review fit for the concierge beta. No account is created. Nothing is provisioned until we talk.
Used only for this beta request and essential Pyre updates.Privacy. No spam. No list sales.