Browse docs
Real projects, and which category they're in#
Self-host, wrap a hosted API, or use a unified API#
Self-hosting a scheduling application gives you control and no vendor lock-in, at the cost of running it yourself: the database, job queue, token storage and platform API changes. A client library for a hosted vendor removes the multi-platform integration work but still leaves you paying that vendor and building the connect and consent flow for your users.
SkedCast's API is hosted and includes connect links for your end users. Its object model (clients, campaigns, approvals) is built for agencies and teams rather than a single account.
FAQ
- Is there an open-source scheduler I can self-host?
- Yes. Postiz (gitroomhq/postiz-app) is licensed under AGPL-3.0, and its README describes an open-source edition you deploy on your own infrastructure. Source: https://github.com/gitroomhq/postiz-app (checked 2026-11-04).
- Should I build my own wrapper around each platform's raw API?
- Only if you have one or two platforms and want no third-party dependency in the posting path. Beyond that, you re-solve OAuth, token refresh, media processing and rate-limit handling per platform, which is the cost a unified API exists to remove.