Deploy Postiz on a VPS in a few steps
Install Postiz on your own Docker VPS
VPS-1
From
₹420.00
ex. GST/month
₹495.60 incl. GST/month
Specifications:
2 vCores
4 GB RAM
40 GB SSD NVMe
Daily backup of the previous 24 hours
VPS-2
From
₹810.00
ex. GST/month
₹955.80 incl. GST/month
Specifications:
4 vCores
8 GB RAM
75 GB SSD NVMe
Daily backup of the previous 24 hours
VPS-3
From
₹1160.00
ex. GST/month
₹1368.80 incl. GST/month
Specifications:
6 vCores
12 GB RAM
100 GB SSD NVMe
Daily backup of the previous 24 hours
VPS-4
From
₹2240.00
ex. GST/month
₹2643.20 incl. GST/month
Specifications:
8 vCores
24 GB RAM
200 GB SSD NVMe
Daily backup of the previous 24 hours
Installing Postiz manually on a Docker VPS
A manual installation of Postiz on a Docker VPS begins with a clean server base: an up-to-date system, secure SSH access, and resources adapted to the expected load. Once Docker and Docker Compose are installed, Postiz is deployed from a compose file that describes the necessary services, their ports, their volumes, and their dependencies. Environment variables then centralise sensitive or usage-specific configuration, such as public URLs, application secrets, database parameters or external integrations. By associating Docker volumes with persistent VPS storage, you retain data, media and configurations beyond restarts or updates. This approach requires more expertise than a one-click deployment, but it offers precise control over the architecture, security and evolution of your Postiz instance.
Installing and managing Postiz in self-hosting
Deploying Postiz cleanly on a Docker VPS
Start by preparing a clean VPS with Docker and Docker Compose installed, then create a directory dedicated to Postiz in order to isolate the configuration, persistent volumes and environment files. Manual deployment generally consists of retrieving the compose file, defining the necessary variables in a .env file, then launching the containers with docker compose up -d. It is recommended to place Postiz behind a reverse proxy such as Traefik, Caddy or Nginx, with a valid TLS certificate, a dedicated domain name and HTTPS redirection rules. This foundation ensures stable access to the interface, whilst facilitating updates, backups and log monitoring.
Configuring the environment and network access
Before the first connection, check the services expected by the application: database, queue, media storage and public variables used to construct callback URLs. The most frequent errors stem from an incorrectly declared domain, a port not correctly exposed or an inconsistent OAuth callback between Postiz and social platforms. Once the containers have started, check the status with docker ps, consult the logs with docker logs and test access to the dashboard from the final domain, not just from the server's IP address.
Connecting social networks with OAuth
After opening the interface, create the first administrator account, then configure the social integrations one by one. Each network generally requires a developer application, API credentials, a client secret and a redirection URL corresponding to your self-hosted instance. This step must be handled with precision: an incorrect callback URL or incomplete OAuth permissions will prevent publishing, even if the account appears connected. Once the tokens have been generated, Postiz can centralise authorised profiles and prepare posts without multiplying manual connections to the different platforms.
Structuring the shared editorial calendarëlëmentsia ԥхынۃ
The editorial calendar becomes the central point of your organisation. You can plan content by channel, campaign, brand or period, then adapt the texts, visuals and schedules according to the constraints of each network. In a self-hosted installation, the benefit is also operational: media remains processed by your own infrastructure, teams work in a common space, and drafts can be structured before validation. To maintain good performance, monitor disk space, the size of imported files and the available bandwidth, especially if you are planning many images or short videos.
A cloud base ready for operation
Mastering the advanced Postiz Docker environment
Orchestrating Postiz with Docker Compose
A clean Postiz deployment generally relies on a docker-compose.yml file that describes the entire stack: main application, background services, database, cache or processing queues depending on the chosen architecture. This approach makes the environment explicit, versionable and reproducible. Dependencies are no longer installed manually on the VPS: they are declared, isolated and restarted in a consistent manner with Docker Compose.
Centralising the configuration in a .env file
The .env file centralises sensitive settings and variables: Public instance URL, application secrets, database credentials, SMTP settings, social network OAuth keys or connection options to external services. By separating the configuration from the compose, you can adapt Postiz to a domain, a test environment or production without modifying the application image. It is also a healthier basis for backups, secret rotations and controlled updates.
Understanding Postiz application services
Postiz works with several application building blocks that must communicate in a stable manner: web interface, API, workers, publication scheduling, data storage and auxiliary services. Docker allows you to isolate each role in its container, while linking them via a dedicated internal network. This separation facilitates diagnosis: you can consult the logs of a specific service, restart a component without disrupting the entire stack and identify a connection, queue or database error more quickly.
Protecting data with persistent volumes provided by the
Critical data must never depend on the lifecycle of a container. Persistent volumes retain the database, generated files, imported media and elements necessary for the sustainable operation of the instance. A serious strategy provides for named volumes, regular backups, a tested restoration procedure and particular attention to permissions. This is what allows you to update or recreate containers without losing history or operational configuration.