Deploy and Host Postiz on Railway

Postiz is an open-source social media scheduler. Write a post once, schedule it for X, LinkedIn, Bluesky, Mastodon, Instagram, Facebook, Threads, YouTube, TikTok, Reddit and more than 20 other networks, and let Postiz publish it on time. It includes a calendar, team workspaces, analytics, a public API and an MCP server for AI agents.

About Hosting Postiz

This template runs Postiz with everything it needs: the Postiz app, a Temporal server that schedules and publishes posts, Postgres and Redis. Your account is created on first boot from the email you enter and a generated password, and sign-ups stay closed, so nobody else can claim your instance.

After deploying, open the Postiz URL and sign in with POSTIZ_ADMIN_EMAIL and POSTIZ_ADMIN_PASSWORD from the Postiz service's Variables tab. Then add channels: each social network needs a developer app whose keys you set as variables on the Postiz service.

The template pins the Postiz and Temporal versions. A GitHub Action picks up new Postiz releases the same day, runs the full stack through a smoke test, and only then publishes the update. Railway then shows an "update available" notice in your project, and you apply it when it suits you.

Common Use Cases

Schedule posts to many social networks from one calendar
Run social media for several brands or clients with separate workspaces
Let AI agents draft and schedule posts through Postiz's API or MCP server
Keep your posts, media and channel tokens on infrastructure you control

Dependencies for Postiz Hosting

Postgres for Postiz data and Temporal history
Redis for caching and rate limits
Temporal for scheduling and publishing

Deployment Dependencies

Postiz: https://github.com/gitroomhq/postiz-app
Postiz docs: https://docs.postiz.com
Temporal: https://github.com/temporalio/temporal
This template's source: https://github.com/aimranov27/postiz-railway

Implementation Details

Uploaded images and videos are stored on a volume mounted at /uploads and served from your Postiz URL, where social networks fetch them when publishing. Everything else, including Temporal's databases, lives in Postgres.

Compared with Postiz's own docker-compose, this template drops Elasticsearch, the second Postgres, the Temporal UI and admin tools. Temporal stores its search data in Postgres instead, which saves about 1 GB of RAM.

It also fixes problems that break a plain Postiz deploy on Railway. Login cookies are rewritten to your app's host, because browsers reject Postiz's default .railway.app cookie. Postiz waits for Temporal before starting its workers, a watchdog restarts the workers if they stop polling, and an hourly job publishes posts that were missed.

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.