🔥
HotRepo
nitter — Self-host Alternative Twitter front-end
📦
zedeus

nitter — Self-host Alternative Twitter front-end

Alternative Twitter front-end

⭐ 14.5k🍴 1.4kNim📜 agpl-3.0🐳 Docker Compose#nim#privacy#self-hosted#twitter

nitter

Alternative Twitter front-end

⭐ 14,479 stars on GitHub · 🍴 1,369 forks · 📜 License: agpl-3.0 · 💻 Language: Nim

What is nitter?

A standout opensource self-host project on GitHub — host on your own server for full control over your data and costs.

Main components

  • No JavaScript required
  • Zero ads
  • All requests go through the backend, client never talks to Twitter
  • Prevents Twitter from tracking your IP or JavaScript fingerprint
  • Uses Twitter's unofficial API (no developer account required)
  • Lightweight (for @nim_lang, 60KB vs 784KB from twitter.com)
  • RSS feeds (instance-specific, often disabled due to abuse)
  • Mobile support (responsive design)

The biggest strength is active opensource community — fast bug fixes, regular features, no abandonment risk.

Best for self-host enthusiasts wanting to try a strong-community opensource project.

Topics: the project is tagged with popular topics:

  • 🏷️ nim
  • 🏷️ privacy
  • 🏷️ self-hosted
  • 🏷️ twitter
  • 🏷️ x

Quick install

The project supports Docker Compose:

git clone https://github.com/zedeus/nitter.git
cd nitter
docker compose up -d

Check the README in the repo for required env variables.

Minimum system requirements

Component Recommended
RAM 1024 MB
CPU 1 vCPU
Disk 15 GB SSD
OS Ubuntu 22.04 LTS / Debian 12
Docker 24.0+

⚡ Deploy fast on VSIS

Use the VSIS VPS Mini 1GB RAM / 1 vCPU / 15GB SSD (~70k/tháng) plan from VSIS.NET — high-speed VN-based VPS, 24/7 support, ideal for running nitter smoothly.

🎯 Benefits:

  • One-command docker compose up -d deploy in 2 minutes
  • Dedicated IPv4, root access, unmetered domestic bandwidth
  • Daily snapshot backup
  • Free install assistance from the VSIS team

👉 See matching VPS plans at vsis.net

Resources


Article compiled from GitHub data on 10/10/2026. Star/fork counts may have changed — see live numbers via the GitHub link.