Deploy Postiz
Schedule posts to X, LinkedIn, Instagram and more from your own server.
temporal-admin-tools
Just deployed
elasticsearch-railway
Just deployed
/esdata
temporal-postgres
Just deployed
/var/lib/postgresql/data
postiz_redis
Just deployed
/data
temporal-ui
Just deployed
postiz_postgres
Just deployed
/var/lib/postgresql/data
postiz-app
Just deployed
/uploads
temporal_server
Just deployed
Deploy and Host Postiz on Railway

Postiz is an open source social media scheduling and management platform. Teams plan, write, schedule and analyze posts for X, LinkedIn, Instagram, Facebook, TikTok, YouTube, Reddit, Bluesky, Mastodon, Threads, Pinterest, Discord and more from one calendar. It also has a public API, webhooks, an n8n node and an MCP server, so you can schedule posts from your own code, automations or AI agents. Postiz is AGPL-3.0 licensed with about 41,900 GitHub stars, and v2.26.0 shipped in November 2026; this template follows the latest Postiz image. It deploys the full current stack on Railway: the Postiz app, PostgreSQL, Redis, and the Temporal workflow engine that publishes scheduled posts, with Elasticsearch for Temporal. Hosted schedulers such as Buffer and Hootsuite charge per channel or per seat, roughly $5 to $100+ per month (approximate). Postiz on Railway costs about $20–40/month for unlimited channels and team members.
What This Template Deploys
| Service | Purpose |
|---|---|
| postiz-app | ghcr.io/gitroomhq/postiz-app, the web app, API and workers behind nginx on port 5000 with a public domain. Volume at /uploads for media. |
| postiz_postgres | PostgreSQL for users, channels, posts and analytics, private only. |
| postiz_redis | Redis 8.2 for queues and caching, with a volume at /data. |
| temporal_server | temporalio/auto-setup, the workflow engine that runs scheduled publishing. |
| temporal-postgres | A separate PostgreSQL database for Temporal. |
| elasticsearch-railway | Elasticsearch for Temporal's workflow search, with a generated password and a volume at /esdata. |
| temporal-ui | Temporal's web UI for inspecting workflows, private only. |
| temporal-admin-tools | Temporal CLI tools for maintenance. |
Everything talks over Railway's private network. Only Postiz itself has a public domain.
About Hosting Postiz
Social media tools usually bill per connected channel and per team member, so costs climb as a brand grows. Postiz gives you the same planning workflow on your own server, with no channel limits and your content, drafts and analytics in your own database.
Calendar and scheduling. Plan posts on a week or month calendar, schedule them for the best time, and reuse content across channels with per-network edits.
Many networks. Connect X, LinkedIn, Instagram, Facebook, TikTok, YouTube, Reddit, Pinterest, Threads, Bluesky, Mastodon, Discord, Slack and more.
Team collaboration. Invite teammates, assign roles, leave comments and run an approval step before posts go live.
Public API and webhooks. Create and schedule posts from your own backend, and react to events with webhooks.
Automation. Use the official n8n node, or tools such as Make and Zapier through the API, to post from feeds, forms or spreadsheets.
AI agents. Point the Postiz MCP server or CLI at your instance so assistants can draft and schedule posts.
AI writing and images. Bring your own OpenAI key to generate post ideas, captions and images.
Analytics. See engagement per post and channel where the network's API provides it.
Deploy Postiz in Under 5 Minutes
- Click Deploy on Railway. All passwords and secrets are generated for you.
- Wait for
temporal_serverandpostiz-appto finish starting; the first boot runs database migrations. - Open the Postiz domain and register the first account right away.
- Add developer app credentials for each network you want, such as
LINKEDIN_CLIENT_IDandLINKEDIN_CLIENT_SECRET, topostiz-appand redeploy. - Connect your channels in Postiz and schedule your first post.
Important: Sign-Up and Social App Keys
Sign-up is open. DISABLE_REGISTRATION is false, so anyone who finds the URL can create an account. After your team has joined, set it to true on postiz-app and redeploy.
You bring your own social apps. Self-hosted Postiz cannot use Postiz's hosted, pre-approved apps. For each network, create a developer app on that platform, set its callback URL to your Postiz domain, and add the client ID and secret as variables. Some platforms, such as Meta, YouTube and TikTok, review apps before they can post publicly, which can take time.
Common Use Cases
- Agencies: manage many client brands and channels without per-channel fees.
- Startups: keep a steady posting schedule across X, LinkedIn and Bluesky.
- Content teams: draft, review and approve posts together before they publish.
- Developer relations: announce releases automatically from CI through the API.
- Automation workflows: post new blog articles or products from n8n or Make.
- AI-assisted posting: let an AI agent draft and schedule posts through MCP.
- Communities: schedule updates to Discord, Mastodon and Reddit from one place.
- Privacy-minded brands: keep unreleased campaigns on your own infrastructure.
Configuration
| Variable | Service | Default | Description |
|---|---|---|---|
MAIN_URL / FRONTEND_URL | postiz-app | Railway domain | Public address of Postiz |
NEXT_PUBLIC_BACKEND_URL | postiz-app | domain plus /api | API address used by the browser |
JWT_SECRET | postiz-app | 🔐 Auto-generated | Signs login tokens; keep it stable |
DISABLE_REGISTRATION | postiz-app | false | Set to true after your team signs up |
STORAGE_PROVIDER | postiz-app | local | Media saved on the /uploads volume |
TEMPORAL_ADDRESS | postiz-app | temporal_server, port 7233 | Workflow engine address |
ELASTIC_PASSWORD | elasticsearch | 🔐 Auto-generated | Read by Temporal by reference |
POSTGRES_PASSWORD | both databases | 🔐 Auto-generated | Database passwords |
Social network credentials. Add variables such as X_API_KEY, X_API_SECRET, LINKEDIN_CLIENT_ID, REDDIT_CLIENT_ID, FACEBOOK_APP_ID, YOUTUBE_CLIENT_ID and TIKTOK_CLIENT_ID with their secrets. Only the networks you configure appear in Postiz.
Custom domain. Add it to postiz-app in Railway, update MAIN_URL, FRONTEND_URL and NEXT_PUBLIC_BACKEND_URL, and update the callback URLs in each social developer app.
Media storage. Uploads live on the /uploads volume. For larger media libraries, switch STORAGE_PROVIDER to Cloudflare R2 with its variables.
Email. Add an email provider so password resets and team invitations are sent.
Backups. Back up postiz_postgres and the /uploads volume together. Temporal's database holds workflow state and can be backed up as well.
Memory. Temporal and Elasticsearch need the most memory. The Elasticsearch heap is set to 512 MB; raise it in ES_JAVA_OPTS if Temporal reports search errors.
Upgrades. Postiz follows the latest image, so a redeploy can pick up a new release. Back up Postgres first and read the release notes for migration steps.
Postiz vs. Alternatives
| Feature | Postiz on Railway | Buffer | Hootsuite | Mixpost |
|---|---|---|---|---|
| Hosting | Self-hosted | Hosted SaaS | Hosted SaaS | Self-hosted |
| License | AGPL-3.0 | Proprietary | Proprietary | MIT core, paid Pro |
| Public API | ✅ | Limited | Paid plans | Pro |
| Unlimited channels | ✅ | Per channel | Plan limits | ✅ |
| Team approvals | ✅ | Paid plans | ✅ | Pro |
| MCP and n8n | ✅ | ❌ | ❌ | ❌ |
| Price | About $20–40/month total | About $5–10/channel/month | About $99+/user/month | Hosting plus license |
Buffer is simple and polished. Hootsuite adds enterprise listening and reporting. Mixpost is another self-hosted option. Postiz combines a scheduler with an API, MCP and automation on your own server.
Dependencies for Postiz Hosting
- A Railway account.
- Developer app credentials for each social network you want to post to.
- Optional: an OpenAI API key and an email provider.
Deployment Dependencies
- Postiz on GitHub: source code and releases
- Postiz documentation: providers, configuration and API
- Temporal: the workflow engine behind scheduled posts
Implementation Details
Inside the Postiz container, nginx on port 5000 routes /api to the backend on port 3000 and everything else to the frontend. Scheduled posts are Temporal workflows, so they survive restarts and retry on temporary network errors.
Frequently Asked Questions
What is Postiz? An AGPL-3.0 open source social media scheduler with a calendar, team workflow, public API and AI features.
How much does it cost to host Postiz? About $20–40/month on Railway for all eight services, with no channel or seat limits.
Why can't I connect a network?
Add that network's developer app credentials to postiz-app and set the app's callback URL to your Postiz domain.
How do I stop strangers from signing up?
Set DISABLE_REGISTRATION to true on postiz-app and redeploy.
Can I schedule posts from code? Yes. Create an API key in Postiz settings and call the public API, or use the n8n node.
What does Temporal do here? It runs the workflows that publish each scheduled post at the right time.
Why Deploy and Host Postiz on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Postiz on Railway, you get a full social media scheduler with an API for your whole team, with unlimited channels and your content on your own infrastructure.
Template Content
temporal-admin-tools
temporalio/admin-toolselasticsearch-railway
praveen-ks-2001/elasticsearch-railwaytemporal-postgres
ghcr.io/railwayapp-templates/postgres-sslpostiz_redis
redis:8.2.1temporal-ui
temporalio/uipostiz_postgres
ghcr.io/railwayapp-templates/postgres-sslpostiz-app
ghcr.io/gitroomhq/postiz-apptemporal_server
temporalio/auto-setup