Deploy Postiz LinkedIn

Schedule LinkedIn posts from your own Postiz server

Deploy Postiz LinkedIn

Just deployed

Just deployed

/data

Just deployed

/uploads

/var/lib/postgresql/data

Deploy and Host self hosted Postiz LinkedIn (Open-Source LinkedIn Post Scheduler) on Railway

This template runs Postiz on Railway so you can connect LinkedIn profiles and company pages and schedule posts from your own server.

About Hosting Postiz LinkedIn open-source software on Railway (self hosted Postiz LinkedIn scheduling template)

Your posts, drafts and connected LinkedIn tokens live on your own server rather than inside a hosted scheduler's database.

Why Deploy Postiz LinkedIn, the Buffer alternative on Railway (Railway Free Trial)

Buffer charges per channel, so a founder with a personal profile and two company pages pays for three seats of the same tool every month.

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 LinkedIn 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 LinkedIn self hosting

Railway skips the server work, but a VPS can be cheaper if you don't mind managing one.

ProviderWhat You Get with RailwayWhat You Get with the Other Provider
DigitalOceanOne-click deploy of postiz, Temporal, Postgres and Redis, with an HTTPS domain ready for LinkedIn callbacks.A bare Droplet where you install Docker, run the compose file, and handle the proxy and TLS yourself.
AWSPrivate networking between the four services and persistent volumes, with no VPC to configure.Full control over EC2, RDS and ElastiCache, but more setup and less predictable pricing.
HetznerEverything wired together from one template, with no server sizing or Temporal upkeep.Cheap CPU and RAM per euro, with updates, backups and HTTPS all on you.

Pick Railway if you want LinkedIn working today, and a VPS if you'd rather spend a weekend on ops to save a few dollars.

Common Use Cases for hosted Postiz LinkedIn

  • A founder posting on a schedule: Write a week of posts on Sunday and queue them for weekday mornings. The Advertising API scope keeps the token alive so the queue doesn't die by day three.
  • Company page posts from a team calendar: Marketing, product and sales share one calendar. The LinkedIn Page provider posts under the company name, not a personal account.
  • Agencies running several pages: Keep five client pages on one self-hosted instance instead of paying per channel on a SaaS plan.
  • Reusing one draft across channels: Write the core idea once, then adapt it for LinkedIn and shorter posts on X or Bluesky from one composer.
  • Approval before posts go out: A writer drafts, a manager reviews, and only then does the post get scheduled. Drafts stay off the company page until they're approved.

Dependencies for Postiz LinkedIn Docker hosted on Railway

This template runs four services: the Postiz app, Temporal for scheduling, Postgres for data, and Redis for queues. All four are needed to schedule and publish posts.

Deployment Dependencies for Managed Postiz LinkedIn Service (Social Media Scheduling)

The postiz service uses the official Postiz image and serves the frontend, the /api backend, and workers from one container on public port 5000.

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

Set the domain variables first, because the LinkedIn OAuth redirect depends on them.

MAIN_URL=https://RAILWAY_PUBLIC_DOMAIN
FRONTEND_URL=https://RAILWAY_PUBLIC_DOMAIN
NEXT_PUBLIC_BACKEND_URL=https://RAILWAY_PUBLIC_DOMAIN/api
JWT_SECRET=generated-64-char-secret
TEMPORAL_ADDRESS=temporal-private-domain:7233
STORAGE_PROVIDER=local
UPLOAD_DIRECTORY=/uploads
NOT_SECURED=true
DISABLE_REGISTRATION=false
LINKEDIN_CLIENT_ID=from-linkedin-developer-app
LINKEDIN_CLIENT_SECRET=from-linkedin-developer-app

NOT_SECURED=true lets login cookies work on the default Railway domain. Set DISABLE_REGISTRATION to true once your first account exists.

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

Postiz vs Buffer (Hosted Social Scheduler Alternative)

  • Where Postiz wins: You own the server and the data, with no per-channel plan that grows as you add company pages.
  • Where Buffer wins: It is hosted, so there is nothing to deploy or patch, and LinkedIn connects without a developer app.
  • Setup cost: With Postiz you create the LinkedIn app, add the products and set redirect URIs yourself.

Postiz vs Hootsuite (Enterprise Social Management Alternative)

  • Where Postiz wins: A solo founder or small agency can run it on a cheap Railway service instead of paying per seat.
  • Where Hootsuite wins: It brings listening, reporting and large-team governance that Postiz does not match.
  • Maintenance: Hootsuite is someone else's problem at 2 a.m., while your Postiz instance is yours to update.

Postiz vs Taplio (LinkedIn-Focused Tool Alternative)

  • Where Postiz wins: It covers LinkedIn alongside other networks in one calendar, and the data stays on your server.
  • Where Taplio wins: It is built around LinkedIn growth, with post ideas and engagement tools Postiz lacks.
  • Hosting: Taplio runs for you, while Postiz asks you to keep a deployment healthy.

Postiz vs Native LinkedIn Scheduling (Built-In Post Composer Alternative)

  • Where Postiz wins: You can schedule posts for several profiles and company pages from one calendar, which LinkedIn's composer does not do well.
  • Where native LinkedIn wins: It needs no app registration, tokens or server, so it is the fastest way to post one update.
  • Reliability: Native scheduling never breaks on an expired token, while Postiz depends on the LinkedIn scopes and token refresh staying in order.

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

Once the deploy is live, connecting LinkedIn takes about fifteen minutes. Follow these steps in order.

  1. Create an app in the LinkedIn developer portal and link it to a company page.
  2. On the Products tab, add Share on LinkedIn, Sign In with LinkedIn using OpenID Connect, and the Advertising API.
  3. Submit the Advertising API access form, or token refresh won't work.
  4. On the Auth tab, add https://your-postiz-domain/integrations/social/linkedin as a redirect URI, plus the linkedin-page version for company pages.
  5. Confirm the Auth tab lists openid, profile, w_member_social, r_basicprofile, rw_organization_admin, w_organization_social and r_organization_social.
  6. Copy the Client ID and Client Secret.
  7. On the Postiz service in Railway, add these variables and redeploy.
LINKEDIN_CLIENT_ID=your-client-id
LINKEDIN_CLIENT_SECRET=your-client-secret
  1. In Postiz, add a channel. Choose LinkedIn for a profile or LinkedIn Page for a company page.
  2. Authorise the connection, then compose and schedule a post with an image if you like.

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

Any VPS with Docker works, but you need a domain with HTTPS because LinkedIn's OAuth callback must reach your server.

Clone the Repository

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

Install Dependencies

Install Docker and the Compose plugin, then confirm they run. The official compose file from docs.postiz.com starts Postiz with Postgres, Redis and Temporal.

docker compose version

Configure Environment Variables

Set MAIN_URL and FRONTEND_URL to https://your-domain and NEXT_PUBLIC_BACKEND_URL to https://your-domain/api.

MAIN_URL=https://your-domain
FRONTEND_URL=https://your-domain
NEXT_PUBLIC_BACKEND_URL=https://your-domain/api
LINKEDIN_CLIENT_ID=your-client-id
LINKEDIN_CLIENT_SECRET=your-client-secret

Start the Postiz LinkedIn Application

Bring the stack up in the background and watch the logs.

docker compose up -d
docker compose logs -f postiz

Railway handles the domain, HTTPS, volumes and service wiring for you, which is most of what makes it quicker than running the VPS yourself.

Official Pricing of Postiz LinkedIn (Postiz pricing)

Postiz LinkedIn is free and open source under AGPL-3.0, so running the self-hosted version costs you nothing in licence fees.

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

Self hosting means you own the server, the data and the LinkedIn connections, and you pay for hosting instead of a monthly seat.

Monthly cost of self hosting Postiz LinkedIn on Railway

Railway bills by usage, so the total depends on how much the app, Temporal, Postgres and Redis use.

System Requirements for Hosting Postiz LinkedIn on a VPS

On a VPS, plan for roughly 2 GB of RAM or more, since the stack runs Postiz, Temporal, Postgres and Redis together.

Frequently Asked Questions (FAQs)

Why does Postiz need the Advertising API product?

LinkedIn only issues refresh tokens to apps with the Advertising API product approved.

What does the NotEnoughScopes error mean?

LinkedIn logged the user in but issued a token missing one or more scopes Postiz needs.

What is the difference between the LinkedIn and LinkedIn Page providers?

The LinkedIn provider posts as your personal profile, while LinkedIn Page posts as a company page you administer.

How long do the LinkedIn tokens last?

Access tokens last about 60 days.

Can I post images and documents?

Yes, images go to the /uploads volume and attach to LinkedIn posts.

Does LinkedIn limit how often I can post?

LinkedIn applies rate limits per app and per member, so many posts in one day can be rejected. Spacing scheduled posts across the week avoids most of these problems.


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