brainstormity/LightPost

LightPost is a lightweight, self-hosted social media scheduler. You connect accounts, write content once, then publish immediately or queue it, while the app tracks each destination separately. It suits an individual or small team that wants one private dashboard instead of hopping between platforms, and is comfortable running a Python service.

What it does

A single composer fans out one post to multiple accounts, including several accounts on the same platform. Each destination can receive text, images or both, subject to that platform's limits. Posts can be saved as drafts, duplicated, scheduled in the browser's timezone, or sent now. Per-account delivery results include links to published posts; failed destinations can be retried without re-sending successes, or abandoned. The queue persists across restarts, overdue schedules resume, and saved media-processing progress survives too. See the feature list and platform table in the README.

Supported publishing targets are Bluesky, Mastodon, X, Instagram, Threads, Discord webhooks, LinkedIn personal profiles, Telegram channels and Facebook Pages. TikTok, Pinterest and Google Business Profile are marked under development. Images are limited to 1 MB each and must be imported from direct public HTTPS JPEG URLs; for Instagram, Threads and Discord the image URL must stay available until delivery finishes. Videos are not supported at all.

How it runs

It is one Python process plus SQLite and plain HTML/CSS/JavaScript, with no external database, frontend build step or AI dependency. The documented requirements are Python 3.11+ on Linux or macOS; Node.js is only used for development checks and formatting. The setup command sequence and an optional systemd service file are provided in the project repository.

Because scheduling runs in the app, it must stay running for posts to go out on time, and it is a single-owner application: run one process per database and keep SQLite on local storage. Beyond loopback, ADMIN_PASSWORD is required at 16+ characters, and COOKIE_SECURE should be enabled when serving over HTTPS. Access should be over a trusted network or HTTPS.

Credentials, costs and limits

You bring your own authorized platform credentials. Initial OAuth consent flows are not included, so connecting an account means obtaining credentials from each platform first. API fees, token expiry, permissions and account eligibility still apply. X additionally requires confirming API cost before publishing or scheduling.

Backups must include the entire data directory and .env together, with the encryption key preserved. Post-history exports omit credentials and image files, so they are not full backups. Delivery is not atomic or guaranteed exactly once: if a platform accepted a post before a connection dropped, check the destination before retrying.

HotRepo's take

HotRepo recorded LightPost on its NEW-REPOSITORY board at 196 total stars on 2026-10-29. That single dated observation is not a measure of daily growth or momentum.