Postwright documentation
Postwright turns one video into a week of content and, on Pro, runs a full content operating system — blog, newsletter, social cadence, editorial AI, and SEO. It’s self-hosted: it runs on your machine and publishes to destinations you own.
Read this first
Postwright is powerful because it publishes for you — but publishing means it needs somewhere to publish to. The video engine (Studio) posts to YouTube, LinkedIn, and Meta out of the box. Pro adds a blog pipeline and a newsletter engine, and those need a destination you control.
A self-hosted site — a Git repo on GitHub, deployed on Vercel, with email through Resend — works with zero custom code (it’s the exact stack Postwright was built on). Other destinations range from a little setup to not supported. Before you buy Pro, read How publishing works so there are no surprises.
Browse the docs
Install & setup
Prerequisites, the guided installer, and the one-time platform logins.
How publishing works
The one thing to read first: where Pro can and can’t publish your blog — and the self-hosted stack that works out of the box.
Newsletter
Resend or Mailgun, drip sequences, and subscriber management.
Social platforms
YouTube, LinkedIn, Instagram, Facebook, and Threads — which need a login and which need API keys.
Configuration
The environment variables you set, grouped by concern.