Postiz

Bring scheduled publishing for many networks into one workflow

Postiz centers on placing posts into a calendar and schedule and publishing them to each service at the requested time. Its integration manager currently contains providers for X, LinkedIn, Instagram, Facebook, Threads, YouTube, TikTok, Pinterest, Reddit, Discord, Slack, Mastodon, Bluesky, Telegram, WordPress, Medium, dev.to, and many others. Service-specific behavior is encapsulated in each provider, allowing the user-facing workflow to manage very different destinations through one operational surface.

Sources: [1][2]

Connect analytics and team workflows to external automation through the Public API

The README lists analytics, team collaboration, comments, and shared scheduling alongside a Public API for automation. A Node.js SDK, an n8n custom node, and a Make.com integration are also provided, so publishing can originate from a CMS, internal tool, or generative-AI workflow instead of only from the Postiz calendar. Several providers, including X and YouTube, implement analytics methods, reinforcing the design goal of keeping publishing and performance checks in the same system.

Sources: [1][2]

For teams that want multi-brand, multi-channel publishing with self-hosting and automation options

Postiz fits product teams, marketing and communications groups, agencies, and creators who publish repeatedly across several networks. It is particularly useful when scheduling is only one part of the workflow and you also want n8n or Make to create posts, an internal system to call a Public API, or teammates to review and comment before publishing. The README currently states that there is no feature difference between the hosted and self-hosted versions, making it a candidate for organizations that want to retain control of the application and operational data.

Sources: [1]

Self-hosting means operating both the platform and each social network's OAuth integration

A self-hosted installation requires infrastructure such as Postgres and Redis and service-specific client IDs, client secrets, or bot tokens for the networks you connect. OAuth reviews, permissions, rate limits, and publishing rules remain platform-specific and cannot be normalized away by Postiz, so every destination still requires its own developer configuration and policy review. The stack also includes Next.js, NestJS, Prisma, and Temporal, giving it more operational surface area than a single-binary scheduler.

The repository is licensed under AGPL-3.0. If you modify Postiz and make that modified version available to users over a network, the Affero GPL has stronger source-availability obligations for network use than ordinary permissive licenses. Internal deployments, customer-facing hosted services, and customized distributions should evaluate those terms separately from the API and data policies of each social network or AI service connected to Postiz.

Sources: [1][3][4]