PostSider is an open-source social publishing scheduler built around 33 registered platform connectors, durable background workflows, and several ways to manage publishing: a web dashboard, REST API, Node.js SDK, and MCP server. The number is a count in the project’s README, not a guarantee that every connector supports the same post formats, actions, or account types. The project’s author describes the design in his account of how PostSider works; the project README documents its current connector list and setup.
How PostSider handles different platforms
Publishing to multiple networks is not one uniform operation. Each service can have its own authentication flow, API, post formats, media and text limits, validation rules, analytics, and token-refresh requirements. A scheduler that treats every destination as identical would have difficulty representing those differences.
As an Amazon Associate I earn from qualifying purchases.
PostSider’s answer is to put each platform integration behind a shared provider contract. The README names the SocialAbstract/SocialProvider pattern: the application can ask a provider what it supports and use that provider to carry out the relevant action, while platform-specific behavior remains inside the integration. An integration manager makes registered providers available to the rest of the application.
In the author’s words, “So one of the most important decisions in PostSider was to isolate each platform behind a common provider interface.” A new provider is registered through integration.manager.ts and has associated frontend metadata, according to the project documentation. The intent is to give the application a common way to work with integrations without pretending their capabilities are identical.
#1 Best Overall
Which platforms are listed as supported?
The project README listed 33 active connectors when accessed on October 7, 2026. The list below is the project’s registry, not an independent verification of each service’s current API or of successful publishing from every account.
Social and creator platforms
- X
- LinkedIn Profile and LinkedIn Page
- Instagram via Facebook and Instagram Standalone
- Threads
- YouTube
- TikTok
- Bluesky
- Mastodon
- Nostr
- Farcaster
- Lemmy
- Twitch
- Dribbble
- Google Business Profile
- Whop
- Moltbook
Chat and community
- Discord
- Slack
- Telegram
Blogs and publishing
- Dev.to
- Hashnode
- Medium
- WordPress
- Ghost
- Blogger
- Notion
- Mataroa
- Write.as
- Listmonk
Connector presence alone does not establish that a particular action, format, or account is available to you. Before depending on a connector, check its current provider documentation and whether your account and any required platform app or API access are eligible for the action you want.
How scheduled posts survive a server restart
A simple timer inside a web server process is tied to that process: if the process stops, its in-memory timer stops with it. PostSider’s documented design instead separates application data from long-running background work. The NestJS API stores application data in PostgreSQL, while Temporal coordinates durable workflows handled by workers. Those workers carry out work such as calling platform providers. The project also uses Temporal workflows for token refresh.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →This explains the design goal: scheduled work is not meant to depend on the lifetime of a single web process. It does not establish a particular uptime, delivery-success rate, or guarantee that an external platform will accept a post. Publishing still depends on the relevant provider, credentials, platform rules, and service availability.
What the software runs on
PostSider is documented as a TypeScript monorepo rather than a single executable or static site. The README lists Next.js 15 and React 19 for the frontend, NestJS 11 for the API, PostgreSQL with Prisma 6.5, Redis, and Temporal. Storage can be configured for local files, Cloudflare R2, or MinIO. Sentry monitoring is listed, while OpenAI-powered AI features and Polar.sh billing are optional. Authentication options listed include JWT, GitHub OAuth, Google OAuth, and generic OIDC. These are versions and options in project documentation and may change as the repository evolves.
Can you self-host PostSider?
Yes. The project documents a Docker Compose route for local evaluation and a separate production setup for internet-facing deployments. The local route brings up PostgreSQL, Redis, and Temporal along with the application. It is a multi-service deployment, so self-hosting means operating and maintaining more than the web interface.
Start a local evaluation
- Clone the project repository from GitHub.
- From the repository, run
docker compose up -d. - Bootstrap the initial administrator using the project’s setup instructions.
- Open the local service on port
4007.
Use the README’s current setup instructions for the exact bootstrap procedure. The project says credentials are needed only for providers you intend to use. Its documentation states, “You configure credentials only for the platforms you actually use.”
Plan a production deployment
For production, the README directs operators to its separate production setup and self-hosting guide. Its production stack includes the app, PostgreSQL, Redis, MinIO, Temporal, and supporting services, and expects production secrets. In practice, assess who will handle upgrades, backups, database and cache operations, workflow infrastructure, storage, and secret management before choosing to self-host.
Dashboard, API, SDK, and agent workflows
The dashboard is not the only documented way to operate PostSider. Its public REST API is exposed under /public/v1 and uses an organization API key. The Node.js package is @postsider/node; the project’s examples cover scheduling posts and listing posts or channels.
The @postsider/mcp server is described as a thin interface over the public API, with 19 tools. They cover actions such as listing connected channels, reviewing calendars, creating drafts, requesting approvals, uploading media, managing scheduled posts, and reading analytics. The README frames agent use as read-first and draft-first, with a deliberate publishing action rather than automatic posting as the default assumption.
AI functionality is optional. The project says it works without an OpenAI API key; without one, AI features remain disabled. Using the API, SDK, or MCP interface does not remove the need to configure the relevant account credentials or satisfy platform-specific requirements.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteSecurity controls and the AGPL-3.0 license
The project README lists encrypted provider credentials at rest, optional TOTP two-factor authentication with recovery codes, organization-wide 2FA enforcement, an activity trail, secure httpOnly cookies, CORS and CSP controls, rate limiting, and server-side authorization and plan enforcement. These are controls described by the project, not the result of an independent security audit.
Best Value
PostSider is licensed under AGPL-3.0. The README says that if you run a modified version as a network service, you must make the corresponding source code available to users of that service. Read the repository’s license and consult qualified legal guidance for how the terms apply to your deployment.
What to check before adopting it
The most useful assessment is whether PostSider fits the accounts, workflows, and operational responsibilities you actually have:
Quick Recap
- Target actions: Confirm that the exact accounts, post formats, and actions you need are supported by the relevant connector.
- Platform access: Check OAuth or app approval requirements, account eligibility, and per-platform limits.
- Operations: Decide who will run and maintain the database, cache, workflow engine, storage, upgrades, backups, and secrets if self-hosting.
- Workflow interfaces: Determine whether the dashboard is enough or you need the API, SDK, MCP tools, or approval steps.
- Optional components: Decide whether the AI and billing integrations are useful for your deployment.
- License fit: Review AGPL-3.0 against your intended use, especially if you plan to modify and operate the software as a network service.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
