Social media decision
X Posts
A competent technical user can build and self-host a minimal replacement in about a week using existing APIs and libraries; the product's value is in convenience and packaging rather than durable proprietary moats.
Visit website↗Built by Matt, who ships 8 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off21 h to build
$2.1/mo6 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All X Posts alternatives, with the arithmetic →
What a replacement has to do
- Learn user persona from their X account, find trending threads (HN/Reddit/RSS), generate post drafts via Grok/xAI, schedule and auto-post to the user's X developer app.
What it still won’t have
- Vendor-provided polished UX and bundled updates/support
- Any proprietary integrations or comparisons maintained by the vendor
- Automatic future product improvements and built-in commercial competitor pricing comparisons
- A paid product's bugfix and customer support SLA
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
X Posts does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted X post generator and scheduler using Next.js (React) deployed on Vercel, Node.js serverless API routes, PostgreSQL (or SQLite) for minimal storage, and AWS S3-compatible blob storage. Core features in scope: (1) Persona importer: fetch recent tweets using an X Bearer Token and extract persona metadata; (2) Trend collector: fetch Hacker News, Reddit, and RSS feeds and normalize results; (3) Generation integration: call xAI/Grok API to produce hooks and drafts given persona + trend inputs; (4) Scheduler/auto-poster: OAuth-based X Developer app integration to schedule and publish posts, including image support; (5) Web UI: persona setup, draft editor, schedule calendar, and job status. Out of scope: multi-team billing, analytics dashboards beyond basic post history, paid UI theming. Include environment variable handling, secure storage of keys only in deployment env (never store vendor keys in DB), error handling for API failures and rate limits, unit and integration tests for persona import, generation calls, and posting flows, and deployment scripts for Vercel. Provide a README with step-by-step setup and a sample .env.example.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score93
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productxposts.co — homepage
- official pricingxposts.co — pricing and details
- official pricingxposts.co — cost estimate
- open sourcegitroomhq/postiz-app
- open sourceLocoreMind/locoagent
Integrity checks
What held up, and what did not.
