Deploy Postiz X

Schedule posts and threads to X from your own Postiz

Deploy Postiz X

/var/lib/postgresql/data

Just deployed

Just deployed

/data

Just deployed

/uploads

Deploy and Host self hosted Postiz X (Self-Hosted Scheduler for X Posts and Threads) on Railway

This template deploys Postiz with its own X developer app wired in, so you can queue posts and threads to X from a scheduler you control.

About Hosting Postiz X open-source software on Railway (self hosted Postiz for X (Twitter) scheduling template)

This template runs the official Postiz image, which bundles the frontend, backend API, and workers in one container.

Railway handles provisioning, the private network between Temporal and the app, volumes, and a public HTTPS domain for X's OAuth callback.

Why Deploy Postiz X, the Typefully alternative on Railway (Railway Free Trial)

If you live in Typefully mostly to queue threads, you're paying a monthly fee for a scheduler you could run yourself.

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 X 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.

Railway vs Other Hosting Providers and VPS for Postiz X self hosting

Here is how the options compare for this four-service stack.

ProviderWhat You Get with RailwayWhat You Get with the Other Provider
DigitalOceanOne click deploy of the app, Temporal, Postgres and Redis with no server patching.A droplet you size, secure and patch yourself, with Docker Compose on you.
AWSSimple service wiring and usage billing without learning VPCs or IAM first.Deep control and scale, but a small Postiz X stack takes far more setup time.
HetznerDomains, HTTPS and volumes handled for you, so the OAuth callback just works.Lower raw price per RAM, but you run Caddy or nginx and certificates yourself.

Pick Railway if you want Postiz X running this afternoon, and a VPS if you like owning every layer.

Common Use Cases for hosted Postiz X

  • Queuing a week of threads: Write five or six threads on Sunday, paste each one into the editor as multiple values so every reply lands in sequence, and set them to go out across the week without touching X in between.
  • Cross-posting launch announcements: Draft one launch note once and schedule it to X alongside your other connected networks, so the announcement goes out everywhere at the same moment.
  • Team review before posts go out: Invite a teammate to check the wording and any Made with AI or paid partnership labels before a post is scheduled, which catches mistakes that are hard to undo on a public feed.
  • Recycling evergreen posts: Keep your best-performing tips in a queue and reschedule them every few months, so older material keeps earning impressions without you rewriting it.
  • Scheduling at audience time slots: Pick the hours your followers are most active, then queue posts for those slots instead of posting whenever you happen to have a free minute.

Dependencies for Postiz X Docker hosted on Railway

Postiz X runs as four services on Railway: the postiz app, Temporal 1.28.1, Postgres 18 and Redis 8.2.

Deployment Dependencies for Managed Postiz X Service (Social Media Scheduler)

  • postiz: the app container, public on port 5000, with a volume at /uploads and a health check on /.
  • Temporal 1.28.1: runs scheduled posts on the private network at port 7233, storing its data in Postgres.
  • Postgres 18: the main database, passed to the app as DATABASE_URL.
  • Redis 8.2: the cache and queue store, passed to the app as REDIS_URL.
  • X developer app: created in the X developer portal, with X_API_KEY and X_API_SECRET set on the postiz service.

Implementation Details for Postiz X (Using Postiz official docker image)

Set MAIN_URL and FRONTEND_URL to https://RAILWAY_PUBLIC_DOMAIN, and NEXT_PUBLIC_BACKEND_URL to the same domain with /api added.

How does Postiz X compare against other ways to schedule posts to X

Postiz vs Typefully (Typefully Alternative)

  • Scope: Typefully is a SaaS built around writing and scheduling for X and LinkedIn. Postiz covers 20+ networks, so it fits if you post to more than X.
  • Hosting: Typefully runs on its servers. Postiz runs on your own Railway project, so your posts and API keys stay with you.
  • Where Typefully wins: It's polished and needs no setup. If you only want to schedule X threads and don't want to manage an X developer app, Typefully is the faster path.

Postiz vs Buffer (Buffer Alternative)

  • Pricing model: Buffer charges per channel on its SaaS plans. Self-hosting Postiz means you pay Railway usage instead of a per-channel subscription.
  • Control: Postiz is AGPL-3.0 and you can read and change the code. Buffer is closed.
  • Where Buffer wins: It has a mature mobile app, broad team workflows and support you can call. Postiz leaves those to you.

Postiz vs Hypefury (Hypefury Alternative)

  • Focus: Hypefury is built for X growth, with scheduling, queues and engagement tools. Postiz focuses on scheduling and publishing across networks.
  • Ownership: Postiz stores your data in your own Postgres and runs on your domain. Hypefury keeps your data on its platform.
  • Where Hypefury wins: Its X-specific growth features are deeper. If audience growth tooling matters more than owning the stack, Hypefury is the better fit.

Postiz vs native X scheduling (X Built-in Scheduler)

  • Threads: Native X scheduling handles single posts well but is limited for threads. In Postiz you add more values to one post and each becomes a reply in sequence.
  • Team review: Postiz lets you invite teammates and review posts before they go out. Native X has no approval step.
  • Where native X wins: It needs no developer app, no callback URL and no hosting. For occasional single posts, it's the simplest option.

How to use Postiz X (the OSS social media scheduler)?

Once the deploy is green and you've signed up, you need an X developer app before Postiz can post anything.

  1. In the X developer portal, create a project and an app inside it.
  2. Under User authentication settings, set App permissions to Read and Write and Type of App to Native App. Postiz uses OAuth 1.0a, and any other app type fails with error 32.
  3. Set the Callback URI to https://your-domain/integrations/social/x and add your website URL.
  4. Under Keys and Tokens, copy the API Key and API Key Secret.
  5. Add them to the postiz service and redeploy:
X_API_KEY=your-api-key
X_API_SECRET=your-api-key-secret
  1. In Postiz, click Add Channel, choose X, and approve the connection.
  2. Create a post or thread. For a thread, add more values in the editor, one per reply, then pick a time slot and schedule it.

If the connect step fails, check the callback URL first, since it has to match your domain exactly.

How to self host Postiz X on other VPS Services (Postiz self hosting guide)

Clone the Repository

Grab the Postiz source from GitHub and move into the project folder. You'll need git and Docker on the machine first.

git clone https://github.com/gitroomhq/postiz-app.git
cd postiz-app

Install Dependencies

The stack runs in Docker, so you don't install Node or Postgres by hand. Give the box roughly 2 GB of RAM or more.

Configure Environment Variables

Set your domain and secrets in the compose environment. Your domain needs HTTPS, because X's OAuth callback will only work over a real URL.

MAIN_URL=https://your-domain
FRONTEND_URL=https://your-domain
NEXT_PUBLIC_BACKEND_URL=https://your-domain/api
X_API_KEY=your-x-api-key
X_API_SECRET=your-x-api-secret

Set the X callback in the developer portal to https://your-domain/integrations/social/x, or sign-in will fail.

Start the Postiz X Application

Bring the stack up in the background, then open your domain to reach the /auth sign-up page. The first account you create becomes the admin.

docker compose up -d

Railway handles all of this for you, including the domain, HTTPS and the four services.

Official Pricing of Postiz X (Postiz pricing)

Postiz is open source under AGPL-3.0, so self hosting it is free. Check the pricing page before you decide.

Postiz X cloud vs self hosted comparison (Pricing, features, costs, and more)

Postiz has a hosted cloud at postiz.com with paid monthly plans, and self hosting is free. Check current plan pages before you commit.

Monthly cost of self hosting Postiz X on Railway

Railway bills by usage, and a light setup with the postiz app, Temporal, Postgres and Redis usually lands around $10-25 a month.

System Requirements for Hosting Postiz X on a VPS

Plan for roughly 2 GB of RAM or more, since the stack runs four services at once.

Frequently Asked Questions (FAQs)

Why does Postiz use OAuth 1.0a for X?

Postiz talks to the X API through the OAuth 1.0a flow, so the app in the X developer portal has to be set to Native App.

Why do I get a callback mismatch error when connecting X?

The callback URI in the X developer portal has to match your domain exactly, which is https://your-domain/integrations/social/x.

How do threads work in Postiz?

Add more values to a single post in the editor and each one becomes a reply in sequence.

Can I post to several X accounts from one Postiz?

Yes, you add each X account as its own channel with Add Channel, and then choose which channels each post goes to.

Does X charge for API access?

X sets its own API access tiers and posting limits, and those change over time, so check the developer portal for your current plan.

Why are my links getting stripped from posts?

That happens when STRIP_LINKS_FROM_X_POSTS is set to true, which removes URLs from the post text before it publishes.


Template Content

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
50
View Template
Foundry Virtual Tabletop
A Self-Hosted & Modern Roleplaying Platform

Lucas
71
View Template
Letta Code Remote
Run a Letta Code agent 24/7. No inbound ports, just deploy.

Letta
51