centrifugal.dev valid

Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.

Manage this listing — optional · Visit publisher ↗

Claim my listing on Agent Web Map for centrifugal.dev:
1. POST https://agentwebmap.com/v1/sites/centrifugal.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://centrifugal.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/centrifugal.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/centrifugal.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory. Ownership management is optional.

Centrifugo

Centrifugo is a scalable open-source real-time messaging server. It instantly delivers messages to application clients connected over WebSocket, HTTP-streaming, Server-Sent Events (SSE), WebTransport, or GRPC, organized around a PUB/SUB channel model. Centrifugo is language-agnostic: it runs as a standalone server in front of a backend written in any language — a self-hosted alternative to PubNub, Pusher, Ably, and Socket.IO.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T18:22:28.446Z. Cached copy · Source on centrifugal.dev

# Centrifugo

> Centrifugo is a scalable open-source real-time messaging server. It instantly delivers messages to application clients connected over WebSocket, HTTP-streaming, Server-Sent Events (SSE), WebTransport, or GRPC, organized around a PUB/SUB channel model. Centrifugo is language-agnostic: it runs as a standalone server in front of a backend written in any language — a self-hosted alternative to PubNub, Pusher, Ably, and Socket.IO.

Typical usage: your application backend publishes events to channels via the Centrifugo server API, and Centrifugo fans them out to all online subscribers. Centrifugo handles persistent connections, horizontal scaling (via Redis or Nats engines), channel history and recovery on reconnect, online presence, and client authentication/authorization. The links below point to the documentation for the latest version (v6).

## Getting started

- [Introduction](https://centrifugal.dev/docs/getting-started/introduction): what Centrifugo is, its background and core concepts.
- [Quickstart](https://centrifugal.dev/docs/getting-started/quickstart): build a simple real-time app with Centrifugo step by step.
- [Main highlights](https://centrifugal.dev/docs/getting-started/highlights): summary of Centrifugo's key features and capabilities.
- [Design overview](https://centrifugal.dev/docs/getting-started/design): idiomatic usage, message delivery model, history and scalability guidelines.
- [Installation](https://centrifugal.dev/docs/getting-started/installation): install via Docker, binaries, packages, or Kubernetes.
- [Integration](https://centrifugal.dev/docs/getting-started/integration): how to integrate Centrifugo with your application backend.
- [Comparing with others](https://centrifugal.dev/docs/getting-started/comparisons): Centrifugo vs your own WebSocket server, Socket.io, Pusher/Ably/PubNub, Redis, Kafka, Nats.
- [Real-time for AI apps](https://centrifugal.dev/docs/getting-started/ai-apps): streaming LLM responses and other AI real-time patterns.
- [Ecosystem](https://centrifugal.dev/docs/getting-started/ecosystem): SDKs, backend framework integrations, and community tools.

## Transports and client SDKs

- [Transports overview](https://centrifugal.dev/docs/transports/overview): all supported client transports and when to use each.
- [WebSocket](https://centrifugal.dev/docs/transports/websocket): primary bidirectional transport.
- [HTTP-streaming](https://centrifugal.dev/docs/transports/http_stream): bidirectional transport over fetch streaming.
- [SSE (EventSource)](https://centrifugal.dev/docs/transports/sse): bidirectional emulation over Server-Sent Events.
- [WebTransport](https://centrifugal.dev/docs/transports/webtransport): experimental transport over HTTP/3.
- [Client SDK API](https://centrifugal.dev/docs/transports/client_sdk): common behavior of official client SDKs (reconnect, state, tokens).
- [Client real-time API](https://centrifugal.dev/docs/transports/client_api): subscriptions, publish, history,
…

Help agents understand your site

Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.

Manage this listing → · Agent and API instructions

Machine-readable: GET /v1/resolve?q=centrifugal.dev · GET /v1/domain/centrifugal.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain