Source: gitroomhq/postiz-app GitHub repository (29.2k stars, AGPL-3.0, v2.21.6)

Postiz is the largest open-source AI-enhanced social media scheduling platform — 29.2k stars, AGPL-3.0, supports 14 social networks, fully self-hostable. NextJS + NestJS + Prisma + Temporal monorepo with native AI content generation, AI scheduling, and a Postiz Agent CLI for autonomous-agent integrations. The open-source answer to Buffer / Hootsuite / Later, with a sharper automation surface (N8N node, Make, Zapier, NodeJS SDK).

Key Takeaways

  • 29.2k stars puts it well ahead of any other open-source social scheduler — effectively the open-source default for self-hosted social media management.
  • 14 social networks supported: Instagram, YouTube, Dribbble, LinkedIn, Reddit, TikTok, Facebook, Pinterest, Threads, X (Twitter), Slack, Discord, Mastodon, Bluesky.
  • AI is first-class, not bolt-on. AI content generation, AI scheduling, and a dedicated Postiz Agent CLI for agent-system integration.
  • AGPL-3.0 is meaningful. Self-hosting permitted. Any SaaS built on top of Postiz must release source. Blocks proprietary forks while keeping the community version free.
  • Automation surface is broad. Custom N8N node, Make integration, Zapier integration, NodeJS SDK (@postiz/node), and the Postiz Agent CLI for direct agent-system integration.
  • Tech stack matches modern Node monorepo conventions: Pnpm workspaces, NextJS frontend, NestJS backend, Prisma ORM (PostgreSQL default), Temporal for workflow orchestration, Resend for email.
  • Hosted SaaS available at platform.postiz.com for users who don’t want to self-host. Pricing not extracted from the README.
  • Latest version v2.21.6, released 2026-04-12 — actively maintained.

Why It Matters for This Wiki’s Domain

Dental marketing / WEO Marketly context

  • WEO Marketly manages 10 dental sub-accounts in GoHighLevel. Each likely needs presence on multiple social networks. A self-hosted Postiz on Railway / VPS centralizes that without per-channel Buffer subscription costs.
  • AI content generation can be wired to WEO brand guidelines via system prompts — closes the gap between OmniPresence dental scripts (the content) and the daily posting cadence (the distribution).
  • Postiz Agent CLI + Hermes = automated dental content posting. Hermes generates / approves the assets, Postiz handles scheduling and multi-network distribution.
  • AGPL is acceptable for internal use — WEO isn’t building a SaaS on top of Postiz, just running it.

Agency client management

  • Team collaboration and per-account separation make Postiz viable as a white-label social manager.
  • Single instance covers what would otherwise require Buffer ($6+/mo per channel) + team collab + Hootsuite-style analytics + an automation layer.
  • Self-hosting eliminates per-seat / per-channel licensing that scales poorly with client count.

Implementation

Tool/Service: Postiz (gitroomhq/postiz-app)

Setup:

  1. Choose deployment model.
    • Hosted: sign up at platform.postiz.com (no setup, pricing on platform).
    • Self-host: see steps below.
  2. Self-host:
    • git clone https://github.com/gitroomhq/postiz-app
    • Set up PostgreSQL.
    • Configure environment variables per docs.
    • pnpm install && pnpm dev for development, or use Docker compose for production.
  3. Connect social network accounts via OAuth from the Postiz dashboard.
  4. Configure team / workspace settings for collaboration.
  5. (Optional) Wire automation: N8N custom node, Make, Zapier, NodeJS SDK, or Postiz Agent CLI.

Cost:

  • Self-hosted: free (infrastructure costs only — Railway / VPS / Render).
  • Hosted: pricing not specified in README; check platform.postiz.com.

Integration notes:

  • N8N custom node — the cleanest integration path if you already run N8N for other automations.
  • Postiz Agent CLI — newest and most agent-native integration. Designed for autonomous workflow contexts (Claude Code, Hermes, OpenClaw).
  • NodeJS SDK (@postiz/node) — for embedding scheduling into custom Node apps.
  • AGPL-3.0 caveat — fine for internal use; if you bundle Postiz into a customer-facing product (white-label SaaS), you must release source code for the entire derivative.
  • Temporal under the hood — production deployments need to plan for the Temporal worker process alongside the NextJS / NestJS apps.

Comparison to Alternatives

ToolTypeAI featuresSelf-hostNetworksPricing
PostizOpen-sourceNative AI generation + scheduling + Agent CLIYes (AGPL)14Free self-host / hosted TBD
BufferCommercial SaaSLimited AI AssistantNo~10$6+/mo per channel
HootsuiteCommercial SaaSOwlyWriter AINo8+$99+/mo
LaterCommercial SaaSAI captions + hashtag suggestionsNo6$25+/mo
MixpostOpen-sourceMinimalYes (MIT)8Free self-host / hosted from $9/mo

Postiz is the most complete open-source option and the only one with a first-class agent CLI.

Try It

  1. Spin up self-hosted Postiz on Railway / Render to evaluate. Time-box to 1 hour. Connect 2–3 social accounts.
  2. Test the AI content generator against a prompt like “Generate 5 posts about [topic] tailored to LinkedIn’s professional tone.” Compare quality to what Buffer / Hootsuite produce.
  3. Wire N8N → Postiz for one workflow (e.g., “every blog post published in WordPress → schedule X / LinkedIn / Threads versions in Postiz”).
  4. Test the Postiz Agent CLI from a Claude Code skill — can it become a callable tool inside an agent workflow that already plans social campaigns?
  5. Evaluate AGPL implications for your context. Most internal-use cases are unaffected; client-facing white-label deployments need legal review.
  6. Benchmark cost vs. paid alternatives — calculate annual savings vs. Buffer / Hootsuite at your account count, and net out infrastructure + maintenance time.

Open Questions

  • Hosted SaaS pricing at platform.postiz.com — not extracted from the README.
  • Which AI model(s) does the AI content generator use? Pluggable (Claude / GPT / local) or fixed?
  • Feature parity vs. commercial competitors on link-in-bio, link tracking, hashtag analytics, optimal-time depth.
  • LinkedIn / X API rate-limit handling — both platforms have aggressive scheduler-tool restrictions; how does Postiz handle them?
  • Postiz Agent CLI invocation pattern — can it be wrapped as a Claude Code skill, or only invoked from a standalone agent runtime?
  • Temporal operational complexity for self-host — is it production-ready out of the box, or does it require Temporal expertise to scale?