Many accounts, isolated
Each account gets its own fingerprint and pinned proxy, so one session problem doesn't spread.
TweetDeck was great for reading timelines. Running many accounts — and answering their DMs — needs a different shape.
Each account gets its own fingerprint and pinned proxy, so one session problem doesn't spread.
Track content and route inbound DMs and comments to a desk instead of juggling browser tabs.
Queue posts and threads across accounts with rate control.
Run it on your own servers with the official API basis.
| Dimension | XControl | TweetDeck lineage | Open-source clients |
|---|---|---|---|
| Status | Actively maintained | Discontinued / paid successor | Community forks |
| Multi-account | Fleet with per-account isolation | Limited | Manual sessions |
| Inbound DMs | Support desk workflow | Basic | None |
| Deployment | Cloud or self-hosted | Cloud only | Desktop |
The official successor moved behind a paid tier with a narrower feature set. XControl targets the fleet case instead: many accounts plus a DM desk.
XControl is not a column client. It is a management and support desk workflow with scheduling, which covers the operational parts TweetDeck users miss.
Each account is isolated with its own TLS fingerprint and pinned egress proxy, and writes are rate-limited with circuit breakers.
TweetDeck was great for reading timelines. Running many accounts — and answering their DMs — needs a different shape.