head to head · open source

Soketi vs Trench

Soketi has 5,634 GitHub stars, 363 forks, 142 open issues and last shipped 1.5 years ago. Trench has 1,663 stars, 64 forks, 3 open issues and last shipped 6 months ago. Soketi leads on adoption by 239% (5,634 vs 1,663 stars). Soketi is written in TypeScript under AGPL-3.0; Trench is written in TypeScript under MIT. Soketi has attracted 6% as many forks as stars, Trench 4%. Trench was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Soketi ★ 5.6K Trench ★ 1.7K category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

Soketi Trench
GitHub stars ★ 5.6K ★ 1.7K
License AGPL-3.0 MIT
Written in TypeScript TypeScript
Last push 2025-03-03 2026-04-06
Forks ⑂ 363 ⑂ 64
Self-hosting Yes Yes
Data ownership Your server Your server

pick Soketi if

  • You weight community size — 5.6K stars and counting
  • You want the AGPL-3.0 license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full Soketi profile →

pick Trench if

  • You want the Trench feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches TypeScript
  • You evaluated both and Trench fits your workflow better

full Trench profile →

About Soketi

Soketi is an open source, Pusher compatible WebSockets server written in TypeScript that lets developers run their own real time channels infrastructure instead of paying for a hosted Pusher plan.

read the full Soketi overview →

About Trench

Trench is an open source analytics infrastructure project written in TypeScript under the MIT license. It is built around Apache Kafka, ClickHouse, and a Node.js based service, and it is distributed as a single production ready Docker image for event tracking. The project sits in the open source event streaming and analytics ecosystem, where teams collect product events, query them quickly, and connect data to dashboards, LLM retrieval pipelines, observability tools, or other analytics products.

read the full Trench overview →

More in Infrastructure & Operations

Immich ★ 114K Uptime Kuma ★ 91K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K Elasticsearch ★ 78K

Related comparisons

automq vs soketi automq vs trench soketi vs timeplus automq vs timeplus automq vs sequin automq vs hook0 automq vs operational automq vs workbench uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana netdata vs grafana uptime-kuma vs huginn worldmonitor vs huginn immich vs paperless-ngx immich vs ceph immich vs filestash immich vs garage immich vs storj immich vs alarik immich vs spinifex paperless-ngx vs ceph

More Messaging & Event Streaming projects

Compare either of these against the rest of the Messaging & Event Streaming field.

Soketi vs AutoMQ Soketi vs Timeplus Soketi vs Sequin Soketi vs Hook0 Soketi vs Operational Soketi vs Workbench

Frequently asked questions

Is Soketi or Trench more popular?

Soketi has 5,634 GitHub stars and Trench has 1,663. Soketi has the larger community by that measure.

Are Soketi and Trench free?

Both are open source. Soketi is licensed under AGPL-3.0 and Trench under MIT. Neither carries a licence fee.

What is the difference between Soketi and Trench?

Soketi is written in TypeScript and Trench in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, Soketi or Trench?

Choose Soketi if you want the larger community (5,634 stars) or its AGPL-3.0 licence terms. Choose Trench if its feature set, stack or MIT licence fits better. Both are self-hostable.