Open-source project
gitroomhq/postiz-app avatar
gitroomhq/postiz-app

Postiz self-hosted: what the Docker setup asks of you before the first post goes out

📨 The ultimate agentic social media scheduling tool 🤖

41,593 stars7,946 forksTypeScriptAGPL-3.0

At a glance

What is it?
Postiz is an AGPL-3.0 social media scheduler with the same feature set in its hosted Cloud and its self-hosted edition. The difference is who owns the infrastructure, the platform developer apps and the AI keys, and the self-hosted side of that bill is larger than the Docker file suggests.
Who is it for?
Self-host Postiz if you need unlimited channels, posts and team members, want scheduling data to stay on your own server, and can wait out platform app approval at Meta, YouTube and TikTok. Choose Postiz Cloud instead if you need those channels working this week, since Cloud ships with pre-approved apps.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • gitroomhq/postiz-app41,593 ★ · +6,767
Star history
Repository2026-08-182026-11-14
gitroomhq/postiz-app34.8k41.6k

6,767 Stars in the last 88 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Postiz Cloud and the AGPL edition run the same product on different owners' servers

Postiz schedules posts across social networks, reports analytics on them and lets a team comment on and schedule posts together. It ships two ways. Postiz Cloud is a hosted subscription with a 7-day free trial, and channels, posts per month and team members are limited by plan tier. The open-source edition is free under AGPL-3.0, you pay only for your own infrastructure, and channels, posts and team members are unlimited.

The project states that it does not gate features or limit the license. Scheduling, calendar views, cross-posting, repeated posts, comments and delays, signatures, RSS auto-post and customer groups are listed as included in both editions. The cost of self-hosting moves elsewhere: into the infrastructure, the platform approvals and the API keys, which the next sections cover.

Self-hosters must get their own developer apps approved at every network

This is the largest practical difference between the editions, and it does not show up in a Docker file. Postiz Cloud comes with pre-approved apps for every channel. A self-hosted install has none: you create your own developer app on each platform and go through that platform's approval. The project warns that Meta, YouTube and TikTok approvals can take weeks.

The consequence is a staged rollout. A team moving off another scheduler can deploy Postiz in an afternoon and still be unable to post to Instagram or TikTok for weeks. The docker-compose.yaml file shows how many credentials are involved: X_API_KEY and X_API_SECRET, LINKEDIN_CLIENT_ID, REDDIT_CLIENT_ID, THREADS_APP_ID, FACEBOOK_APP_ID and more, all empty by default.

Analytics carries the same dependency. In the self-hosted edition analytics is included but requires your own app credentials with analytics scopes, so a platform app approved only for posting will schedule fine and show no numbers.

A pnpm monorepo of Next.js, NestJS, Prisma and Temporal

The codebase is a pnpm workspace monorepo. The frontend is Next.js, the backend NestJS, persistence goes through Prisma with PostgreSQL as the default, scheduled work runs on Temporal, and Resend sends email notifications. The root package.json pins Node to 22.23.4 in its engines field and pnpm to 10.6.1.

The workspace scripts reveal four apps under apps/: frontend, backend, orchestrator and extension, plus an sdk app that publishes the Node SDK. The dev script runs all four in parallel, and dev-backend runs only the backend and frontend. Production start scripts exist per app, such as start:prod:backend and start:prod:orchestrator.

Temporal is the component that sets Postiz apart from a cron-based scheduler. The compose file points TEMPORAL_ADDRESS at temporal:7233, so a self-hosted deployment runs a Temporal server alongside PostgreSQL and Redis. That is three stateful services to back up and upgrade, before counting object storage.

Postiz app Docker setup: the compose file's URLs and secret

The project's Quick Start Guide at docs.postiz.com/quickstart is the official starting point, and Docker, Coolify, Railway and any VPS are named as deployment targets. The repository's docker-compose.yaml runs the image ghcr.io/gitroomhq/postiz-app:latest and opens with the required settings:

yaml
      MAIN_URL: 'http://localhost:4007'
      FRONTEND_URL: 'http://localhost:4007'
      NEXT_PUBLIC_BACKEND_URL: 'http://localhost:4007/api'
      JWT_SECRET: 'random string that is unique to every install - just type random characters here!'
      DATABASE_URL: 'postgresql://postiz-user:postiz-password@postiz-postgres:5432/postiz-db-local'
      REDIS_URL: 'redis://postiz-redis:6379'

Three URL variables point at port 4007 on localhost. For any deployment reached from another machine, those must change to the public address. The .env.example file is blunt that the frontend URL needs to be exactly the URL you access Postiz on, so the localhost values cannot survive into a real deployment. JWT_SECRET ships as a placeholder sentence that must be replaced on every install.

Two more defaults deserve a look. DISABLE_REGISTRATION is 'false', which leaves sign-up open on whatever URL you expose. And the image tag is latest, so pulling and restarting moves you to whatever release is newest.

Local uploads are the default, but avatars and media processing want Cloudflare R2

Storage is where the two configuration files disagree. docker-compose.yaml sets STORAGE_PROVIDER to 'local' with UPLOAD_DIRECTORY at /uploads, and keeps the Cloudflare R2 settings commented out. The .env.example file states that Cloudflare is currently required to save things like social media avatars for accounts, and lists CLOUDFLARE_ACCOUNT_ID, CLOUDFLARE_ACCESS_KEY, CLOUDFLARE_BUCKETNAME and the related keys as required settings.

Every optional media feature also depends on R2. Media normalization, which transcodes web uploads to 1080p h264 mp4 and downsizes images, requires STORAGE_PROVIDER="cloudflare" plus a RunPod Serverless endpoint running postiz-uploader. While it runs, the media record reports status processing until the normalized file replaces the original.

Video clipping goes further. Turning a YouTube video into captioned vertical clips and draft posts needs R2, a RunPod key with access to separate CPU ingest and GPU clipper endpoints, an OPENAI_API_KEY, an Oxylabs account for the uploader to fetch from YouTube, and Deepgram for videos without usable captions. That is five outside accounts for one feature.

AI features run on your keys, and agents reach Postiz through its API

On Cloud, AI Copilot, AI images and AI videos come with monthly quotas and keys managed by Postiz. Self-hosted, they are available only if you bring your own OpenAI or other provider keys, with no quota and the provider's bill landing on you. The Smart Agent likewise needs your own LLM key. An install with no keys set has scheduling without the AI layer.

Automation is a first-class path. Postiz exposes a Public API and webhooks, publishes a Node SDK as @postiz/node, a custom n8n node as n8n-nodes-postiz, and a Make.com integration, and names Zapier among the automation platforms it targets. For AI agents, the project lists an MCP server and an AI Agents CLI alongside dedicated pages for Claude Code, Codex, Cursor and ChatGPT. The practical upshot: an agent or workflow tool can draft and queue posts without anyone opening the calendar UI.

Where Postiz differs from Buffer, and what AGPL-3.0 and fast releases mean

Buffer is the scheduler people most often weigh against Postiz. Buffer is a hosted service only. Postiz Cloud covers the same hosted ground, and the self-hosted edition adds an option Buffer does not have: running the whole scheduler on your own server with your data never leaving it.

The license shapes that option. Postiz is AGPL-3.0, whose network clause means that if you modify Postiz and let other people use your modified version over a network, you must offer them its source. Running an unmodified copy for your own team does not trigger that. Agencies planning a customised, client-facing fork should read the license with that in mind. Contributors sign one of the agreements in ICLA.md or CCLA.md.

Releases move quickly. v2.25.1 shipped on 2026-10-11, v2.25.2 on 2026-10-23 and v2.25.3 on 2026-10-24, and the last push was on 2026-11-02. With the compose file tracking the latest image tag, a self-hoster who pulls regularly takes on every release as it lands.

Editorial conclusion

Self-host Postiz if you need unlimited channels, posts and team members, want scheduling data to stay on your own server, and can wait out platform app approval at Meta, YouTube and TikTok. Choose Postiz Cloud instead if you need those channels working this week, since Cloud ships with pre-approved apps. Before deploying, decide on storage: docker-compose.yaml defaults STORAGE_PROVIDER to local, while .env.example says Cloudflare is currently required to save social media avatars, so plan for an R2 bucket from the start.

Frequently asked questions

How much does Postiz cost?

Postiz Cloud is a subscription priced per plan with a 7-day free trial. The open-source edition is free under AGPL-3.0, and you pay only for your own infrastructure and any AI provider keys you use.

How does Postiz work?

Postiz connects to each social network through a developer app, schedules posts from a calendar and runs the scheduled work through Temporal. It is built on Next.js, NestJS and Prisma with PostgreSQL, and also accepts posts through a Public API, a Node SDK and integrations for n8n and Make.com.

What is the Postiz app?

Postiz is a social media management platform for scheduling, automating and analyzing content. You can use the hosted Postiz Cloud or deploy the AGPL-3.0 open-source edition on your own infrastructure.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/gitroomhq-postiz-app.svg)](https://hysenlabs.com/projects/gitroomhq-postiz-app)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/gitroomhq-postiz-app.svg)](https://hysenlabs.com/projects/gitroomhq-postiz-app)

Was this useful?