# anycable/anycable

Realtime server for reliable two-way communication to power-up any backend

Repository: https://github.com/anycable/anycable
Canonical: https://ross.abutalabs.com/products/anycable
Homepage: https://anycable.io
Language: Go
License: MIT
License Family: permissive
Topics: websockets, realtime, sse
Last push: 2026-08-24T13:36:06+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 96, longevity 100
- inputs: {"age_days": 3651, "days_push": 9, "days_rel": 28, "gap_med": 29.0, "n_releases_24m": 17}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2373, forks 124 (observed 2026-08-28T04:06:41.894164+00:00)

## What it is
AnyCable is an open-source realtime server written in Go that provides reliable two-way communication over WebSockets and SSE with built-in delivery guarantees, message recovery, and presence tracking. It runs as a standalone server alongside any backend (Rails, Laravel, Node.js, Python, or anything via HTTP pub/sub API), supporting 10,000+ connections per server.

## Use cases
- add realtime features to a Rails app with Hotwire and Turbo Streams
- replace Pusher or Reverb in a Laravel application
- power live chat with guaranteed message delivery and recovery
- broadcast events from any backend via an HTTP pub/sub API
- keep WebSocket connections alive during zero-downtime deploys
- track user presence in realtime dashboards
- scale WebSocket connections beyond what a monolith can handle

## When to choose
- you need reliable message delivery with automatic recovery during connectivity issues
- you want a language-agnostic realtime server that works with any backend
- you need to handle thousands of long-lived WebSocket connections with low memory overhead
- you use Rails, Laravel, Hotwire, or Turbo Streams and want first-class integration
- you require self-hosted, HIPAA-compliant realtime messaging

## When to avoid
- you only need simple, low-traffic WebSockets your existing framework already handles
- you prefer a fully managed third-party realtime service without self-hosting
- your use case is one-way push notifications without two-way communication
- you need a realtime server tightly coupled to a specific stack AnyCable doesn't support

## Facets
- artifact type: service
- maturity: stable
- function: websocket, http-server, message-queue, middleware
- domain: web-development, backend
- platform: windows, self-hosted, cross-platform
- tags: websockets, sse, realtime-server, pub-sub, delivery-guarantees, presence, go, rails, laravel, hotwire, real-time, messaging, linux, macos, docker

## Member repositories
- anycable/anycable (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:41.894164+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-30T02:35:05.800852+00:00, confidence not recorded.
  - readme: https://github.com/anycable/anycable (fetched 2026-08-28T04:06:41.894164+00:00, sha fc1b673c04e8)
  - homepage: https://anycable.io (fetched 2026-08-29T10:16:07.213902+00:00, sha 38e154b5c022)
  - site_page: https://docs.anycable.io (fetched 2026-08-29T10:16:07.216655+00:00, sha 04b0ea32cbd1)
  - site_page: https://docs.anycable.io/ (fetched 2026-08-29T10:16:07.218303+00:00, sha 04b0ea32cbd1)
- Data as of 2026-08-30T08:39:29.467469+00:00.