Deploy Postiz
Self-hosted social media scheduler for 30+ networks, with Temporal
Just deployed
/uploads
Temporal
Just deployed
Redis
Just deployed
/data
Just deployed
/var/lib/postgresql/data
Deploy and Host Postiz on Railway
Postiz is an open-source social media scheduler and a self-hosted alternative to Buffer and Hootsuite. You write a post once, then schedule it to X, LinkedIn, Instagram, Facebook, Threads, Bluesky, Mastodon, YouTube, TikTok, Pinterest, Reddit, Discord and more. It includes a calendar, an AI writer, team workspaces, analytics, a public API and webhooks.
About Hosting Postiz
This template runs Postiz v2.26.0 with four services: Postiz, Temporal, Postgres and Redis. Postiz serves the web app, the API and the worker that publishes your posts, behind nginx on one public domain. Uploaded media is stored on a volume and served from that domain, so social networks can fetch it. Temporal schedules and retries every post. It creates and migrates its own databases on the shared Postgres, so no Elasticsearch is needed. Redis handles caching and queues. Temporal, Postgres and Redis stay on the private network. Secrets are generated at deploy, and there is no default password: the first person to sign up owns the instance.
Common Use Cases
- Scheduling a content calendar across many social networks from one place, without per-seat SaaS fees
- Agencies and teams managing several brands' channels, with workspaces, roles and approvals
- Letting scripts or AI agents draft and schedule posts through the Postiz public API
Dependencies for Postiz Hosting
- Postgres (included): Postiz data plus Temporal's two databases
- Redis (included): cache and queues
- Temporal server (included): post scheduling
- Developer app keys for each social network you want to post to
Deployment Dependencies
- Postiz source and releases: https://github.com/gitroomhq/postiz-app
- Postiz self-hosting docs: https://docs.postiz.com/installation/docker-compose
- Social network setup (keys and redirect URLs): https://docs.postiz.com/providers
- Temporal: https://github.com/temporalio/temporal
- Template source: https://github.com/aalfath/postiz-railway-template
Implementation Details
After the deploy finishes, open the Postiz domain and sign up straight away: the first account creates the instance and becomes its admin. DISABLE_REGISTRATION is true, so later visitors can't sign up. Invite teammates from Settings, or set it to false for open sign-up.
To connect a channel, create a developer app with that network, then add its keys as variables on the Postiz service, for example X_API_KEY and X_API_SECRET, or LINKEDIN_CLIENT_ID and LINKEDIN_CLIENT_SECRET. Use https://YOUR-DOMAIN/integrations/social/PROVIDER as the redirect URL. Bluesky, Mastodon and a few others need only a login or token.
Optional: OPENAI_API_KEY turns on the AI features. EMAIL_PROVIDER=resend with RESEND_API_KEY, EMAIL_FROM_ADDRESS and EMAIL_FROM_NAME sends notification emails. For a custom domain, set MAIN_URL, FRONTEND_URL and NEXT_PUBLIC_BACKEND_URL (the domain plus /api) to it.
The login cookie is set for your exact host, not for the shared railway.app parent domain. Postiz and Temporal build from the template's GitHub repo, so you get an update notice in Railway when a new version is merged. Postiz needs about 1.5 GB of RAM, so use a plan that allows it.
Why Deploy 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 are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content