iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
PostSider is an open-source social publishing scheduler built around platform-specific connectors, durable background workflows, and several ways to manage publishing. Its README lists 33 active connectors, but that is a registry count—not a promise that every service supports the same post formats, actions, or publishing behavior.
What the 33-platform count means
The count comes from the project’s registry of active connectors, as documented in its README accessed October 7, 2026. It describes integrations present in the project, not the number of platforms any one user must configure or a measure of successful publishing. As the README puts it, “You configure credentials only for the platforms you actually use.”
The documented connectors are grouped below. Instagram via Facebook and Instagram Standalone, as well as LinkedIn Profile and LinkedIn Page, are listed separately because the project treats them as distinct integrations.
Social and creator platforms
- X
- LinkedIn Profile
- LinkedIn Page
- Instagram via Facebook
- 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 does not establish feature parity. Platforms differ in OAuth and account eligibility, APIs, text and media limits, post formats, analytics, and validation rules. Check the current provider documentation and your account’s eligibility for the specific action you need; the project’s connector list alone does not establish that a platform will approve an app or accept a particular post.
How platform integrations fit together
Each network has its own rules and publishing interface. Rather than building every platform’s behavior into one large publishing path, PostSider puts platform-specific logic behind a shared provider contract. The project describes this pattern with SocialAbstract and SocialProvider.
An integration manager makes registered providers available to the application. When the application needs to perform an action, it can ask the relevant provider what it supports and how to carry it out. That boundary is where platform-specific authentication, capabilities, and validation can be handled without treating every service as interchangeable.
In the author’s explanation, a new provider is registered in integration.manager.ts and paired with frontend metadata. Lukasz, the PostSider author, described the motivation this way: “So one of the most important decisions in PostSider was to isolate each platform behind a common provider interface.” This is the project’s architectural explanation, not an independent assessment of connector completeness.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteHow scheduled publishing survives a web-process restart
A simple timer such as setTimeout belongs to the server process that created it. If that process stops, its in-memory timer stops with it. PostSider instead documents a flow in which the NestJS API stores application data in PostgreSQL and Temporal coordinates durable workflows executed by workers. Those workers call the appropriate platform provider when a scheduled action is due. The project also uses Temporal for token-refresh workflows.
- The API records application data, including scheduling information, in PostgreSQL.
- Temporal coordinates the workflow independently of the lifetime of a particular web request or API process.
- Workers execute the workflow and invoke the provider for the selected platform.
This design aims to keep scheduled work from depending on one continuously running web process. It does not, by itself, establish a delivery-success rate, uptime guarantee, or immunity from failures in workers, infrastructure, credentials, or external platform APIs.
What the application is built with
The project README describes PostSider as a TypeScript monorepo. Its documented stack includes:
- Frontend: Next.js 15 and React 19.
- API: NestJS 11.
- Data: PostgreSQL with Prisma 6.5, plus Redis.
- Background work: Temporal and workers.
- File storage: configurable local storage, Cloudflare R2, or MinIO.
- Authentication: JWT, GitHub OAuth, Google OAuth, and generic OIDC.
- Optional integrations: OpenAI for AI features, Polar.sh for billing, and Sentry for monitoring.
These are the versions and components listed in the README accessed October 7, 2026; a live repository may change. The project says it can run without an OpenAI API key, with AI features disabled. AI and billing are optional rather than prerequisites for the basic scheduler.
Free tools Windows power users keep installed
One-click scans. No signup required.
Can you self-host PostSider?
Yes. The README documents a Docker Compose route for local evaluation. It is a multi-service application, not a single binary or static website: the default stack includes PostgreSQL, Redis, and Temporal alongside the app.
- Clone the project repository: https://github.com/lumizone/postsider.
- From the repository directory, start the local stack with
docker compose up -d. - Bootstrap the initial administrator using the README’s instructions.
- Open the local service on port
4007.
For an internet-facing production deployment, the README points to a separate production setup and self-hosting guide. Its described production stack includes the application, PostgreSQL, Redis, MinIO, Temporal, and supporting services, and requires production secrets. Operating a self-hosted instance therefore means taking responsibility for the services, credentials, upgrades, backups, and storage configuration. Provider credentials are needed only for the services you plan to connect.
Dashboard, API, SDK, and MCP access
PostSider can be managed through its dashboard or programmatically. The public API is exposed under /public/v1 and uses an organization API key. The project also documents a Node.js package named @postsider/node for actions such as scheduling posts and listing posts or channels.
The @postsider/mcp server is described as a thin interface over the public API, with 19 tools. The README lists tools for tasks including listing connected channels, reviewing calendars, creating drafts, requesting approvals, uploading media, managing scheduled posts, and reading analytics. The project presents agent use as read-first and draft-first, with a deliberate publishing action rather than implicit posting. Tool availability does not establish that every external platform action will be accepted.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Security controls and the AGPL-3.0 license
The project README documents 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 project-described controls, not the results of an independent security audit.
PostSider is licensed under AGPL-3.0. The README says that if you run a modified version as a network service, the corresponding source code must be made available to users of that service. Review the repository’s license and seek qualified legal advice for the details of a particular deployment.
What to check before adopting it
The key decision is not whether a connector appears in a list, but whether the project fits the accounts, workflows, and operational responsibilities you actually have. Check:
- Whether the exact target account and post format or action you need are supported.
- Whether platform OAuth approval, API access, and account limits permit that use.
- Whether you are prepared to operate the database, cache, workflow engine, storage, upgrades, backups, and secrets if self-hosting.
- Whether the dashboard is sufficient or your workflow needs the API, SDK, MCP tools, or approval steps.
- Whether you want the optional AI or billing integrations.
- Whether AGPL-3.0 fits your deployment and distribution plans.
The connector count and architecture described here are project-authored claims. The available documentation does not provide independent performance or reliability benchmarks, comparative pricing, or external validation of every connector’s current platform behavior.
Quick Recap
Sources
- Lukasz, PostSider author, “I Built an Open-Source Social Media Scheduler for 33 Platforms — Here’s How It Works,” DEV Community. The page displays a September 29 posting date; the year is not explicit on the page.
- PostSider project README, accessed October 7, 2026.
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.
