Postiz

Deploy Postiz on a VPS in One Click

Automation & workflowsAI & LLM tools

Self-hosted platform for scheduling and publishing social media posts across multiple networks from one dashboard.

  • Ready in ~7 min
  • Free installation
  • We handle the setup
At a glance
Version
Latest (2.x)
Operating system
Ubuntu Server 24.04 LTS
Minimum RAM
4 GB
License
AGPL-3.0
Addressing
IPv4, IPv6
GitHub
37,000
Deployment~7 min
Open source & self-hosted
VPS plans

Choose a VPS plan for Postiz

Blazing-fast NVMe drives and powerful processors. Take a ready-made plan or build the configuration yourself.
Minex
Perfect for personal projects and small websites.
€3.20/mo
Save €0.80 per month

  • 1 vCPU core
  • 1 GB DDR5 RAM
  • 20 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 1 TB traffic
Basex
A great balance of power and affordable price.
€4.80/mo
Save €1.20 per month

  • 2 vCPU cores
  • 2 GB DDR5 RAM
  • 40 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 2 TB traffic
Most popular
Corex
For growing applications and businesses.
€7.20/mo
Save €1.80 per month

  • 4 vCPU cores
  • 4 GB DDR5 RAM
  • 50 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Midex
Resources for high-load projects.
€9.60/mo
Save €2.40 per month

  • 4 vCPU cores
  • 6 GB DDR5 RAM
  • 60 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Proex
Maximum power and scalability.
€12.00/mo
Save €3.00 per month

  • 6 vCPU cores
  • 8 GB DDR5 RAM
  • 70 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Scalex
Resources for scaling.
€16.00/mo
Save €4.00 per month

  • 6 vCPU cores
  • 10 GB DDR5 RAM
  • 150 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Maxex
A large reserve of power.
€44.00/mo
Save €11.00 per month

  • 8 vCPU cores
  • 16 GB DDR5 RAM
  • 200 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Apex
The top configuration.
€79.99/mo
Save €20.00 per month

  • 16 vCPU cores
  • 32 GB DDR5 RAM
  • 400 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic

What you can do with Postiz

Postiz is an open-source social media scheduling and publishing tool built for marketers, agencies, and solo creators who run several channels — X, LinkedIn, Instagram, Bluesky, Mastodon, Discord, and more — from a single calendar. A Postiz self hosted deployment replaces a stack of native apps with one queue for drafts, approvals, and per-channel analytics.

What sets it apart is a built-in AI content assistant plus an agent-ready API, so automation tools can queue posts without touching the UI at all. That's exactly why vps for Postiz makes sense over a shared cloud tier: your drafts, connected accounts, and OAuth tokens stay on infrastructure you control, with no per-seat limits or platform caps.

The applications screen of the control panel with one-click install

Postiz features

A server surrounded by app icons — applications running on a VPS

Postiz covers the full loop from writing a post to measuring how it performed, without leaving one interface.

01

AI Content Assistant

Rewrites and adapts post copy per platform tone in a couple of clicks.

02

Multi-platform publishing

Queue the same post to X, LinkedIn, Instagram, Facebook, TikTok, Bluesky, Mastodon, and Discord from one calendar.

03

Built-in visual editor

A Canva-style design tool for building creatives directly inside Postiz.

04

Team collaboration

Invite teammates to comment on, approve, or co-schedule drafts before they go live.

05

Per-channel analytics

Pulls engagement stats through each network's own official API.

06

Automation-ready API

Trigger and queue posts programmatically, which is what one click automation Postiz workflows in tools like n8n rely on.

07

Docker-based backend

Ships as a Postiz vps docker stack with PostgreSQL, Redis, and Temporal handling job orchestration behind the scenes.

Requirements

Which server to run it on

Minimum requirements for Postiz and the configuration worth starting with.
Minimum
  • CPU2 vCPU
  • Minimum RAM4 GB
  • Disk40 GB
Recommended
VPS Corex
  • CPU4 vCPU
  • Minimum RAM4 GB
  • Disk50 GB

Installation is free — you only pay for the server

Getting started

How to deploy Postiz

Three steps and the app is running on your server.
Step 1
Choose a server

Pick a plan with headroom above the minimum requirements — Postiz installation brings up eight containers at once, including two PostgreSQL instances, Redis, Elasticsearch, and Temporal, so a thin RAM allocation shows up immediately.

Step 2
Pick the app

Mark Postiz in the app list and the platform deploys the full docker-compose stack for you — that's what it takes to install Postiz on vps without cloning a repository or hand-editing environment files.

Step 3
Get your credentials

Open the app URL and register the first account with your email and password — that account automatically becomes the Postiz organization owner.

Why us

Why Host Postiz on Leneex

Speed, protection and support you can rely on — on every plan, with no hidden limits.
Deployment speed
Postiz's official stack isn't three containers — it's eight, with Temporal and Elasticsearch alongside the app itself. Doing that by hand from a docker-compose repo eats an afternoon; a one-click template turns it into a single wait screen.
Free installation
Because the correct Postiz compose setup involves several interdependent services and environment variables, getting it wrong is easy on a first try. Skipping the install fee removes the main friction point for anyone who hasn't run Temporal before.
DDoS protection
Postiz exposes a public login screen and OAuth callback URLs for every connected social account, which makes it a real internet-facing target, not an internal tool. DDoS filtering matters here specifically because a downed instance also breaks OAuth reconnection for X, LinkedIn, and the rest.
Control and support
Diagnosing why a scheduled post silently didn't fire usually means reading Temporal or worker logs, not clicking through a UI. Root access plus engineers who understand a multi-container stack matter more here than for a single-process app.
99.9% uptime with SLA compensation
Posts are scheduled through Temporal workflows tied to a specific send time — if the server is down at that minute, the post doesn't retry itself into existence later. Uptime isn't cosmetic for a scheduling tool; it's the entire premise of the product.
Flexible payment
Agencies running Postiz for clients often need an invoice for accounting, while solo creators just want a card charge. Both paths being available means the billing setup doesn't dictate who can run the tool.
What to choose

Postiz: Self-Hosted vs Cloud — Which to Choose

We compare cost, control over your data and limits, so the choice is an informed one.
Postiz Cloud
Self-hosted on LeneexRecommended
Resources and limitsShared infrastructure sized to your subscription tierDedicated CPU/RAM for your own instance, including the Temporal and Elasticsearch layer
Control and accessNo server access; configuration limited to what the app UI exposesRoot access to the server, direct database access, custom reverse proxy and domain setup
Feature limitsNumber of connected channels and team seats gated by planFull feature set, no channel or seat caps beyond your own server capacity
ScalingScaling means moving to a higher-priced subscription tierUpgrade the VPS plan whenever the container stack needs more headroom
CostRecurring subscription that scales with channels, seats, or usageFixed VPS price regardless of post volume or channel count
Who it fitsTeams that want zero server maintenance and don't mind platform limitsTeams that want data control and no per-channel billing surprises

Postiz Cloud exists as an official paid option, so the comparison is direct: self-hosting pays off once you're running enough channels or team seats that the subscription cost outgrows a fixed VPS price. Teams that specifically care about where OAuth tokens and drafts are stored also have a clear reason to self-host regardless of volume.

Frequently Asked Questions about Postiz on VPS

What people ask most about Postiz and our servers.

  • Postiz doesn't offer a built-in one-click migration between cloud and self-hosted accounts — you'll need to reconnect your social channels and recreate scheduled posts manually on the new instance.

  • Changing the VPS plan resizes CPU and RAM only; the PostgreSQL volumes holding your posts, drafts, and connected accounts stay untouched, as long as you don't delete the server.

  • Yes — and it's not optional for Postiz specifically, since the app sets secure cookies and requires HTTPS to let you log in and connect social accounts at all.

  • Resource usage is driven mainly by the Temporal and Elasticsearch layer running in the background, not by user count directly, so a small team of 2-3 people fits comfortably even on an entry-level plan.

  • You do — as with any self-hosted app, pulling new versions of the docker-compose stack and running the update is on you, though Leneex support can help if something breaks during the process.

What's already running out of the box

A Postiz vps hosting deployment on Leneex brings up the full official stack in one pass — the Postiz app itself alongside PostgreSQL, Redis, Temporal, and Elasticsearch, each in its own container. Temporal handles the actual job scheduling behind every "post at 9am tomorrow" — it's not a cosmetic dependency, it's what fires your posts on time. Containers restart automatically if they crash, so a brief hiccup on one service doesn't take down the whole stack.

First login

The first account anyone registers on a fresh instance automatically becomes the Postiz organization owner — there's no pre-created admin login to look up. Open the app's URL, fill in an email, a password, and a company name on the sign-up screen, and you're in; if no outbound email provider is configured, Postiz activates the account immediately instead of waiting on a confirmation link. After onboarding, you'll land on an empty weekly calendar — that's expected, since nothing is scheduled and no social channels are connected yet.

What to do right after signing in

Close public registration once your own account exists, so nobody else can create a login on your instance — this is a manual step, not a default. Connecting a social channel requires provider API keys for most platforms (you register a developer app on X, LinkedIn, etc., and paste the keys into Postiz); eight platforms work without any extra configuration.

Deploy Postiz in about 7 minutes

Choose a server — we do the rest: install, configure and send you the credentials.