# turms-im/turms

🕊️ The world's most advanced open source instant messaging engine for 100K~10M concurrent users https://turms-im.github.io/docs

Repository: https://github.com/turms-im/turms
Canonical: https://ross.abutalabs.com/products/turms
Language: Java
License: Apache-2.0
License Family: permissive
Topics: instant-messaging, distributed, java, swift, javascript, turms, storage, chat, c10m, c1000k, ios, android, web, desktop, typescript
Last push: 2026-03-10T02:15:08+00:00

## Health v2 (maintenance only)
Score: 55/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 71, release rhythm 8, longevity 100
- inputs: {"age_days": 2640, "days_push": 177, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1919, forks 306 (observed 2026-08-28T04:05:54.920700+00:00)

## What it is
Turms is an open-source instant messaging engine written in Java designed to scale from 100K to 10M concurrent users. It provides a distributed server cluster (gateway, service, and admin components) with client SDKs for Java, JavaScript, and Swift, deployable via Docker Compose or Terraform.

## Use cases
- build a chat app for millions of concurrent users
- self-host a private instant messaging server
- add real-time messaging to iOS, Android, and web apps
- deploy a scalable IM backend with Docker or Terraform
- run a group chat and message timeline service
- monitor a messaging cluster with Prometheus and Grafana

## When to choose
- you need a highly scalable, distributed IM backend for 100K+ concurrent users
- you want a self-hosted alternative to proprietary chat services
- you need cross-platform client SDKs (Java, JS, Swift) for chat apps
- you want built-in admin tooling and monitoring out of the box

## When to avoid
- you need a tiny embedded chat widget with minimal infrastructure
- your team has no capacity to operate a Java-based distributed cluster with MongoDB and Redis
- you only need simple peer-to-peer messaging without server-side features
- you prefer a managed SaaS chat provider over self-hosting

## Facets
- artifact type: framework
- maturity: active
- function: websocket, http-server, rpc, message-queue, monitoring, chatbot
- domain: messaging-platforms, microservices, backend, web-development, mobile-development, developer-tools
- platform: jvm, cross-platform, self-hosted
- tags: instant-messaging, chat, im-engine, distributed-systems, c10m, real-time-messaging, push-notifications, admin-dashboard, terraform, client-sdks, real-time, javascript, swift, docker, kubernetes, web-server

## Member repositories
- turms-im/turms (main) score 55

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:54.920700+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:09:59.113585+00:00, confidence not recorded.
  - readme: https://github.com/turms-im/turms (fetched 2026-08-28T04:05:54.920700+00:00, sha 12f3c6abd91f)
- Data as of 2026-08-30T08:39:29.467469+00:00.