Deploy OpenPost
Self-hosted social scheduler for X, LinkedIn, Threads and Bluesky
openpost
Just deployed
/data
Deploy and Host self hosted OpenPost (Other) on Railway
This template deploys OpenPost, a self-hosted social media scheduler, as independent community packaging of getopenpost/openpost v7.42.2 (AGPL-3.0-only). It is not affiliated with or endorsed by OpenPost. SQLite and media live on one Railway volume.
About Hosting OpenPost open-source software on Railway (self hosted OpenPost template)
Running OpenPost yourself means your posting calendar, your media library and your social account tokens live in a database you control instead of a hosted scheduler's servers.
Why Deploy OpenPost, the self-hosted social media scheduler on Railway
A hosted social scheduler charges a recurring subscription and keeps your posting history on someone else's servers.
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 OpenPost 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 OpenPost self hosting
Choosing where OpenPost runs comes down to how much server work you want to do yourself.
| Provider | What You Get with Railway | What You Get with the Other Provider |
|---|---|---|
| DigitalOcean | A deploy button, managed HTTPS domain, and a persistent volume at /data. | A droplet where you install Docker, manage the firewall, and set up HTTPS and backups. |
| AWS | A single service with a volume and health check, set up from the template. | Broad control over networking and storage, with more setup before OpenPost runs. |
| Hetzner | Usage-based hosting with the same one-click setup and no server to patch. | Low-cost servers where you control the OS, Docker install and updates. |
Pick Railway for a quick start, and a VPS when you want full control over the host.
Common Use Cases for hosted OpenPost
- Solo creator running one brand calendar: You draft posts, attach images from the media library, and schedule them to X, LinkedIn, Threads and Bluesky from a single calendar instead of opening each app.
- Small team sharing a content queue: Several people compose in the same web UI, with the first registered account acting as the instance admin who can restrict registration later.
- Reusing brand assets across posts: Logos, product shots and short videos live in one media library on the Railway volume, so you upload them once and attach them to many scheduled posts.
- Keeping data in your own project: The SQLite database and uploaded media both sit on the /data volume in one service, so there is no separate database to run or manage.
- Testing a posting workflow before committing: Spin up a private instance, connect your own provider app credentials, and try scheduling before deciding whether a hosted tool fits your needs.
Dependencies for OpenPost Docker hosted on Railway
This template deploys one service, openpost, with one volume for all persistent state. Keep the replica count at one, because local persistent state cannot be shared across replicas.
Deployment Dependencies for Managed OpenPost Service
The openpost service listens on port 8080 behind a Railway HTTPS domain. The health check uses /api/v1/health with a 120 second timeout, and the restart policy is Always.
Implementation Details for OpenPost
The template asks for four variables and needs no input from you. OPENPOST_JWT_SECRET is generated and signs login tokens.
How does OpenPost compare against other tools
OpenPost vs a hosted social scheduler (Hosted Social Schedulers Alternative)
- Data Ownership: OpenPost runs on your own Railway service, with SQLite and media on a volume you control. A hosted scheduler keeps that data on the vendor's servers.
- Cost Model: The upstream project is AGPL-3.0 and free to self-host, so you pay only for the infrastructure you run. Hosted schedulers often charge per account, which can be simpler to budget.
- Setup Effort: A hosted scheduler wins on setup, since you sign up and start posting. OpenPost needs a deploy, a first registration, and your own provider credentials.
OpenPost vs posting from each network app (Native Network Apps Alternative)
- Single Calendar: OpenPost queues posts for several networks from one calendar with a shared media library. Native apps only manage their own network.
- Per-Platform Edits: You can adjust text and media for each account and preview each version. Native apps already match each network's exact formats, which is simpler for one account.
- Inbox and Analytics: OpenPost offers an inbox and analytics for supported networks, though features vary by provider. Native apps expose the full feature set of each network.
OpenPost with Docker vs Railway (Docker Self-Hosting Alternative)
- Control: Running the upstream Docker setup on your own server gives full control over the host, networking, and backups. Railway handles the host, the HTTPS domain, and restarts for you.
- Volume Handling: Railway mounts the volume at /data, and this template uses one replica because local persistent state cannot be shared. On a server, you manage the volume and its backups yourself.
- Image Changes: This template uses an unmodified upstream image with USER root added so the Railway volume is writable. A plain Docker deploy keeps upstream's user unchanged.
How to use OpenPost on Railway?
- Open the public Railway domain and register the first account immediately. That user becomes the instance admin, and registration stays open until an admin restricts it in Settings, Instance.
- Add your own provider app credentials in Settings, Instance, Configuration. Social accounts cannot connect without them.
- Connect your accounts, then compose and schedule posts from the calendar.
- If you add a custom domain, update OPENPOST_APP_URL and OPENPOST_PUBLIC_URL to the same new HTTPS origin.
- Keep one replica, since SQLite and media live on the single /data volume.
Health check: /api/v1/health (timeout 120 seconds)
Restart policy: Always
Volume: /data
Replicas: 1
How to self host OpenPost on other VPS Services (OpenPost self hosting guide)
Clone the Repository
Clone the upstream repository at the pinned release tag, then move into the project folder.
git clone https://github.com/getopenpost/openpost.git
cd openpost
git checkout v7.42.2
Install Dependencies
Install Docker and the Docker Compose plugin on your VPS. You do not need a separate database server, because the default setup stores data in SQLite on local disk.
Configure Environment Variables
Create an environment file with your own generated values.
OPENPOST_APP_URL=https://your-domain
OPENPOST_PUBLIC_URL=https://your-domain
OPENPOST_JWT_SECRET=your-generated-jwt-secret
OPENPOST_ENCRYPTION_KEY=your-generated-encryption-key
Start the OpenPost Application
Use the upstream flow: run the documented Docker Compose default with one container, SQLite and local media storage; see the upstream repository for the exact compose file and current steps.
Pricing and License of OpenPost (OpenPost pricing)
OpenPost is open-source software released under the AGPL-3.0-only license, and this community packaging is free to self-host.
OpenPost hosted vs self hosted comparison (Pricing, features, costs, and more)
This template packages the AGPL-3.0 software. The upstream project also describes OpenPost Hosted, but this packaging is the self-host image only and is not that hosted offering.
Monthly cost of self hosting OpenPost on Railway
Railway billing is usage-based and depends on the RAM, CPU, volume size and services you run. Your cost will vary with how much media you store on the volume and how long you keep it.
System Requirements for Hosting OpenPost on a VPS
Running OpenPost on your own VPS needs enough memory and disk for the container, the SQLite database and the media you store under /data.
After each deploy, open the public domain and confirm the health check passes before you treat the service as ready. Keep one replica of any service that holds local persistent state, because a second replica would not see the same volume data. Copy the generated values from the Variables tab into your own records, and keep signing or encryption keys stable across redeploys. If you attach a custom domain, update the public URL variables to that origin before you rely on callbacks, invites, media links or sign-in. Optional mail, AI or agent features need credentials you supply later and are not required to boot this template. Untested upgrades, backups and restores stay your responsibility; this overview only reports the recorded first-deploy checks. When something fails, start with the service logs and the health path before you rotate generated secrets. The template is zero-input: generated secrets and service references are created at deploy time, so you can open the service as soon as it is healthy. Do not change variable names or values from this overview; set only what you need after the first boot, such as a custom domain or an optional provider key.
Frequently Asked Questions (FAQs)
Who becomes the admin of my OpenPost instance?
The first user who registers on your instance becomes the instance admin.
Can I connect social accounts without provider keys?
No.
Is email verification required?
No. Email is not configured in this template, so verification and password reset emails are not sent.
What should I back up?
Back up the /data volume, which holds the SQLite database and uploaded media.
Is this the same app as Postiz?
No. OpenPost is a different application from Postiz, and this template packages only OpenPost.
Template Content
