LIVE UPDATES FOR YOUR APPLICATION

Your application changes.Your users see it live.

Celeris delivers live messages between any connected clients: browsers, mobile applications, backends, and other services. Users see chat messages, order changes, and live dashboards without a refresh. Your team builds the feature. Celeris manages the connections that carry the messages.

ONE MESSAGE. THREE DELIVERIES.

INTERACTIVE DEMO · NO LIVE CONNECTION
01 / PUBLISHER
↗︎

Order dispatched

orders / dispatch
ACCEPT → ROUTE → DELIVER
Live connections · WebSockets
02 / SUBSCRIBED APPLICATIONS
01Customer applicationSubscribed ·
02Operations dashboardSubscribed ·
03Driver applicationSubscribed ·

Publish a message. Each demo client will show it.

ONE MESSAGE SENT. THREE APPLICATIONS UPDATED.
HOW THE MESSAGES TRAVELBinary-first transportChannels and segmentsYour backend and application stay yours

01 / WHERE CELERIS FITS

Build the experience.
We move the messages.

An order leaves the warehouse. Your server sends this message to Celeris. Celeris sends the message to the connected customer application and to the operations dashboard. Your application shows the new status.

Your team decides what happens, who can see it, and how it appears. Celeris manages the live connections and routes each message to the correct subscribers. Your users connect close to where they are, through AWS Global Accelerator and its 130 Points of Presence in 95 cities across 53 countries. Your database and your business logic stay with you.

Explore the platform →
Your server publishes to Celeris, and Celeris delivers to your customer's app and your ops dashboard. Your clients publish through the same path.
01 — SEND LESS

Less to send.
More room to build.

Small messages add up. Celeris carries your payload as bytes. Thus, you can select compact formats, for example MessagePack or Protobuf. This can decrease the bandwidth and the work of encoding and decoding for each message. The possible savings increase when your traffic grows.

You control the format and the bytes. Celeris does not require a JSON conversion.

One position message. Each format carries the same values.
{"playerId":"p1","x":142,"y":88,"action":"move"}
JSON · UTF-848 bytes
MessagePack32 bytes
Protobuf15 bytes

Protobuf uses a shared schema. The numbers show the measured payload only and do not include the protocol overhead. The results change with the payload and the encoding.

Inside binary messaging ↗︎
02 — PLAN FOR REAL CONNECTIONS

Know what to expect.

Users disconnect. Your application needs a plan for the data that it missed. Messages from one publisher arrive in the order that it sent them. Different publishers do not share one global order. Reconnect recovery is bounded and can have gaps or duplicates. Your stored state lets you reconcile the messages.

How ordering works ↗︎
03 — STAY IN CONTROL · COMING SOON

Your data. Your destination.

Soon, you will export messages to your Kafka or RabbitMQ queue. Your application will persist the data at its own speed. Your database stays off the delivery path.

Explore export connectors ↗︎

02 / HOW YOU USE IT

Connect. Send.
Update the screen.

A channel is a named stream of messages, for example an order or a chat room. Your application subscribes to the channels that it needs.

  1. Connect your application. Authenticate the user. Then subscribe to a channel.
  2. Send a message. A backend, a browser, or any other client publishes the data when something changes.
  3. Show the change. Receive the data. Then update the message, the status, or the chart on the screen.
Open the quickstart ↗︎
ILLUSTRATIVE DATA FLOW · NOT SDK CODE01
YOUR APPLICATION
  Position update
  { playerId: "p1", x: 142, y: 88, action: "move" }

ENCODE WITH YOUR CHOSEN FORMAT
  MessagePack → 32 payload bytes

SEND BYTES THROUGH CELERIS
  Channel → segment → connected clients

DECODE IN YOUR APPLICATION
  Same values. Ready for your interface.

03 / USE CASES

What you can build with Celeris.

All use cases ↗︎
01

AI & agent infrastructure

Keep each agentic session continuous and synchronized. A binary-first transport streams tokens with no required JSON wrapper, over one persistent connection.

  • Binary-first
  • Channels & Segments
  • p95 32ms
02

Chat & messaging

Channels, segments, and presence give you the primitives. Build the chat experience that you want, not the one that an SDK forces on you.

  • Channels & Segments
  • Signed token auth
  • JavaScript SDK
03

Financial data & trading feeds

High-frequency delivery for price ticks, trade events, and market data. Each publisher's sequence stays in order, and payloads are binary. There is no JSON overhead on paths where milliseconds cost money.

  • Binary-first
  • Per-origin ordering
  • p95 32ms
04

IoT & device telemetry

Telemetry with high connection counts for sensors, devices, and edge hardware. Binary payloads can decrease the bandwidth and the parse work at the scale that IoT demands.

  • Binary-first
  • BYOD data export (coming soon)
  • Metered billing
05

Live dashboards

Push metrics, alerts, and data changes to clients as they happen, without a poll loop.

  • Metered billing
  • Multi-region
06

Multiplayer & gaming

Low-latency delivery for game state, player actions, and presence. Segments map cleanly to rooms, lobbies, and matches.

  • Channels & Segments
  • p95 32ms
  • Multi-region

LIVE FEATURES. LESS CONNECTION INFRASTRUCTURE.

Build your next
live feature.

We use Google cookies for analytics and for advertising measurement, only if you allow them. Until you choose, Google sets no cookies. Refer to our Cookie Policy.