Installation options
Choose how to run your own Postiz instance
Postiz is open source and you can run the whole stack yourself. Pick the option that matches how you plan to use it.
Not sure you want to host it? Postiz Cloud runs the same application, with the provider developer apps already registered so you can connect a channel in two clicks.
Recommended options
Docker Compose
Recommended for running Postiz. One command, brings up the app plus Postgres, Redis and Temporal.
Development environment
Recommended for working on Postiz. Runs the monorepo from source with hot reload.
Advanced options
Docker (standalone)
Run the container by hand and bring your own database, Redis and Temporal.
Kubernetes and Helm
Deploy to a cluster with the community Helm chart.
Dev container
A preconfigured VS Code dev container.
Upgrading from v1
Migrating an older install onto the Temporal based stack.
Before you start
System requirements
Minimum CPU and RAM, required services, default ports.
Architecture
What the frontend, backend, orchestrator and Temporal each do.
After it is running
- Register the first user. The first account to sign up becomes the organisation owner. If no email provider is configured, Postiz activates the account immediately and you can log straight in.
- Configure the providers you want. Most platforms need you to register a developer app and supply keys. Eight platforms need no configuration at all. See Provider API keys.
- Put a reverse proxy in front of it. Postiz sets secure cookies, so it expects HTTPS in production. See Reverse proxies.
Once you can log in, the rest of the product works the same as it does on cloud. Head to Schedule your first post.