| Deployment model & API access | A managed, multi-tenant API. There is no dashboard to post from — you call an HTTPS endpoint and PostGate operates the queues, workers, and delivery pipeline for you or your customers. | Primarily a hosted dashboard (plus a free browser extension) that a person logs into to schedule posts. A RESTful JSON API exists, but it's gated to Business and Enterprise plans in good standing — not something a Free or Professional customer can build on. |
| Starting price & free tier | Free sandbox plan, no card required. Paid plans start at $4.00/mo. See /pricing. | Free forever tier (1 user, 3 social accounts excluding X, 10 scheduled posts per account, 24-hour post history). Paid plans price per social account rather than a flat seat: independent pricing trackers put Professional around $4–5/account/month and Business around $8–10/account/month on annual billing, more on monthly billing — a 3-account start runs roughly $12–21/mo depending on tier. See publer.com/pricing for the live calculator. |
| Who owns platform app approval | On the white-label plan, bring your own Meta, TikTok, LinkedIn, and other provider app credentials per organization — your approval status and rate limits are yours alone. See /docs/environments. | Publer is a hosted SaaS, not a self-hosted project — customers connect their accounts through Publer's own shared developer apps. There's no path to bringing your own approved app and reselling access under your own platform-app identity. |
| White-label & multi-tenant support | Every embedded connection environment supports a branded logo, primary color, and a verified custom domain on every plan that enables white-label. See /docs/environments. | Workspaces give an agency a way to organize multiple clients' accounts under one login, and every account can be branded with client details for reports. There's no documented product for embedding a branded, custom-domain connection flow into a third party's own app — Publer's dashboard is used directly, under Publer's own brand. |
| Webhook delivery model | Signed events (HMAC-SHA256 over timestamp and raw body) for post.published, post.partial, and post.failed, plus a test-delivery endpoint. See /docs/webhooks. | Publer's dashboard has an “API & Webhooks” settings tab, but its public docs don't detail a request-signing scheme, a documented event set, or per-target delivery evidence the way a webhook consumer would need to verify authenticity. |
| SDK & developer tooling | Generated clients for six languages/runtimes — Node.js/TypeScript, Python, Go, Ruby, PHP, and .NET — from one OpenAPI contract. See /docs/sdks-mcp. | Publer's API docs describe raw REST endpoints, an async job/poll pattern for post creation, and scoped API keys — but no generated, officially maintained SDKs across multiple languages that we could find. |
| Idempotent retries | A stable Idempotency-Key makes a logical create-post request safe to retry for 72 hours — no accidental duplicate publishes. See /docs/idempotency. | Publer's post-creation docs describe a submit-then-poll job model but don't document an idempotency key or another safe-retry contract for the API — a client that resubmits a timed-out request has to build its own duplicate protection. |
| Bulk scheduling & browser tools | No native bulk/batch endpoint — a caller schedules a queue of posts by issuing individual API requests, or wires one together with an automation tool. See the n8n workflow guide. | A genuine strength: the API accepts a bulk array of posts in one request, and the dashboard has a free Chrome/Firefox/Safari/Edge extension plus an auto-schedule queue that slots new posts into the next open time. |