superx ·

Free · open source · self-hosted

Grow on 𝕏 without living on 𝕏

SuperX is a free, open-source, self-hosted X (Twitter) scheduler and growth tool. Draft and review posts, keep a publishing queue, work through replies, and track results from one application you run yourself.

It is an open-source alternative to superx.so. The source is published on GitHub, while the application and Postgres database run on infrastructure you control.

What it does

A practical workflow for showing up consistently

01

Draft in your voice

Connect your X account and, with an LLM key, turn your own posts and topic notes into editable posts or threads.

02

Review, schedule, and publish

Write a post yourself or approve an AI draft, choose recurring weekly time slots, and let the queue publish with visible failure states.

03

Work through replies and leads

With a public-data source, collect mentions and topic feeds in one inbox. An LLM key adds reply drafts and lead scoring.

04

See what happened

Keep follower and post snapshots, review trends and posting streaks, and file people found by Signals into private contact lists.

Run it yourself

Deploy the app and Postgres with Docker Compose

Start from a clone of the GitHub repository. You need Docker, a domain, two generated application secrets, and X OAuth credentials. Copy the environment template, fill in its required values, then run:

git clone https://github.com/ashishbishnoi18/superx.free.git superx
cd superx
cp .env.example .env
docker compose up -d --build
docker compose exec app /app/bin/migrate

The environment template names every required and optional key. Back up the database, uploads volume, and SUPERX_VAULT_KEY. That key also protects the local XChat identity.

Or let us run it

Two prices, one plan, nothing gated

Self-hosting is free and always will be. If you would rather not keep a server alive, this same code runs here, at roughly what it costs to run. Paying unlocks no features: the software is identical either way and the source is public.

Bring your own keys

$5/month

You supply the X and model keys and pay those providers directly, the same as self-hosting. We keep the machine running.

Keys included

$9/month

Runs on our keys, so there is nothing else to sign up for. Fair-use limits apply to the shared API budget.

Cancel from inside the app at any time. Leaving means cloning the repository, not filing an export request.

Honest comparison

Self-hosted control costs operator time

SuperX suits people who value source access and data control more than a managed setup. A hosted tool is the better trade when you do not want to operate the software or manage separate provider accounts.

Self-hosted SuperX compared with hosted X growth tools
Trade-off Self-hosted SuperX Hosted alternative
Cost No SuperX subscription; you pay for your server and provider usage. A recurring plan usually bundles the application and its operation.
Data Records live in your Postgres database; configured integrations receive data when called. The vendor hosts application data and chooses its integration boundaries.
Operations You deploy, upgrade, monitor, rotate secrets, and restore backups. The vendor handles uptime, updates, backups, and support.
Public X data Discovery, feeds, mentions, and Signals need a data source you configure and fund. A hosted product may include an established corpus and managed data access.
Control Inspect and change the source, database, limits, and deployment. Faster onboarding, but behavior and roadmap remain with the vendor.

FAQ

What self-hosting actually involves

How much does SuperX cost?

The SuperX application costs $0 to download and self-host. You still pay for the server, database storage, and any external APIs you choose to use. There is no SuperX subscription fee for running this code yourself.

Which API keys do I need, and roughly what do they cost?

X_CLIENT_ID and X_CLIENT_SECRET are required for sign-in and publishing. As of August 2026, X lists text-post writes without a URL at $0.015 per request and qualifying owned-post reads at $0.001 per resource. An Anthropic or DeepSeek key is optional for AI features; the configured models range from $0.14 to about $5 per million uncached input or output tokens. TWITTERAPI_IO_KEY is optional for public-post discovery, feeds, mentions, and Signals at about $0.15 per 1,000 returned posts. VOYAGE_API_KEY is optional for semantic search at $0.18 per million tokens for the configured model. Provider prices can change.

Does my data leave my server?

Your application records, encrypted X OAuth tokens, analytics snapshots, drafts, and contact lists are stored in your own Postgres database. Data does leave the box when a feature calls a service you configured: X for sign-in, reads, and publishing; Anthropic or DeepSeek for AI work; twitterapi.io for optional public X data; and Voyage for optional embeddings. SuperX does not include third-party product analytics or telemetry.

Does SuperX work without an LLM key?

Yes, but without AI features. You can connect X, write and edit posts yourself, schedule them, publish the queue, and use the non-AI parts of the app. Voice-profile generation, post and reply drafting, Ask, article drafting, and AI lead scoring require an Anthropic or DeepSeek key.

How is this different from superx.so?

SuperX is an open-source, self-hosted alternative, not the hosted superx.so service. You control the source, database, deployment, and provider accounts, and you do not pay a SuperX subscription. In return, you must handle setup, upgrades, backups, monitoring, and API bills yourself. Public-data features need a source you configure and fund, and the inspiration corpus grows on your instance rather than arriving as a bundled hosted library.