Your marketing spreadsheet has twelve tabs. Every network wants a slightly different caption. Someone still posts the LinkedIn link from their phone at 6 p.m. because the scheduler SaaS hit its seat limit.
Postiz (formerly Gitroom) is the open-source social scheduling stack that grew up in the "agentic" era: ~40k GitHub stars, AGPL-3.0, calendar-first UI, cross-posting to X, LinkedIn, Instagram, TikTok, YouTube, Mastodon, Bluesky, Slack, Discord, and dozens more. Postiz Cloud exists if you want pre-approved OAuth apps; self-hosting keeps drafts, media, and API keys on infrastructure you control — including a Canadian VPS.
What it actually does
Postiz is a social operations hub, not a photo editor. Connect channels (one OAuth identity per network), compose once or per-platform, schedule on a calendar, and let workers publish when the clock hits.
Core workflow:
- Composer — global text with per-channel overrides, media library, previews that mimic each network's layout.
- Scheduling — drafts, calendar slots, "post now," repeats, delays, comments on posts, signatures and sets for campaigns.
- Team — collaborators, customer groups (handy for agencies), internal plugs and RSS-to-post automation.
- Analytics — performance views when platform API scopes allow (self-hosters bring their own app credentials).
- AI & agents — copilot, image/video helpers with your API keys; MCP, CLI, and connectors for Cursor, Claude, ChatGPT, n8n, Make.com.
- Public API & webhooks — wire Postiz into n8n or custom pipelines without clicking the UI.
Tech stack: Next.js frontend, NestJS backend, Prisma on PostgreSQL, Temporal for job orchestration, Redis in typical Docker deploys. That is real software — not a cron script with a logo.
Why self-host?
Data stays in your environment. Scheduled posts, client lists, and OAuth tokens live in your database and object storage, not a multi-tenant US bucket you hope is SOC2'd.
No artificial caps. Upstream's comparison table is blunt: self-hosted Postiz drops cloud limits on channels, posts per month, and team seats — you pay for CPU, RAM, and disk instead.
Agency white-label paths. Canadian shops managing regional clients often want one scheduler per brand on the same Swift Host footprint, with backups and access control they define.
AGPL freedom. Fork, add providers, integrate internal tools — as long as you respect AGPL obligations when you distribute changes.
The catch you must plan for: Meta, YouTube, TikTok, and friends want your developer apps and approval timelines. Cloud Postiz ships pre-approved apps; self-host means paperwork and env vars (Provider API keys in their docs). Budget weeks, not minutes, for Instagram-class integrations.
What running it takes
Follow docs.postiz.com installation guides (Docker, Coolify, Railway, or raw VPS). Expect Postgres, Redis, Temporal, reverse proxy TLS, and persistent storage for uploads.
- RAM — treat it like a small SaaS: 4 GB is a floor for tinkering; production with Temporal and workers wants more headroom.
- Updates — you pull images and run migrations; no managed zero-downtime unless you build it.
- Fast wins — docs list platforms that need no developer app (Bluesky, WordPress, Medium, etc.) so you can prove scheduling before Meta approves your app.
- AI features — bring OpenAI or other keys; usage bills go to you, not Postiz.
Lock the admin URL behind SSO or VPN. Rotate OAuth secrets. Back up Postgres before upgrades — scheduled posts are business-critical data.
Who it's for (and who should skip it)
Good fit: marketing teams cross-posting daily, agencies with many brands, creators who want agent/MCP scheduling from Cursor, automation nerds already running n8n beside WordPress.
Maybe skip it: if you post twice a month on one network, use native scheduling. If you will not maintain OAuth apps or Docker, Postiz Cloud saves pain. If compliance forbids storing social tokens on any server you operate, neither cloud nor self-host fixes policy — legal has to choose.
Hosting it in Canada
Postiz fits our Docker and VPS stacks: Postgres on the same host or managed DB, object storage for media, TLS at nginx, outbound HTTPS to social APIs.
Tell us channel count, team size, and whether you need Meta/LinkedIn on day one if you want a deploy checklist before you register developer apps.
Want one calendar for every network you own? Talk with Swift Host — we are in St. Albert and actually answer the phone.
