Developers

Build live product flows with channels, keys, origins, and server authorization.

DomVia Realtime gives developers a focused path for realtime apps: public keys for clients, secret keys for trusted server code, protected channels for sensitive rooms, and operational signals for launch.

Gatewayws.domvia.net
Latency< 100ms
SDKs5 packages
Uptime99.999%
connection modelactive
client → ws.domvia.net/app/{public_key}
server → authorize private or presence channel
server → publish workflow event
client → receive live state
ws.domvia.net
1,243 events/min42ms avgLIVE
eventchannellatency
message.newprivate-chat.room.4212ms
typing.startedprivate-chat.room.426ms
presence.updatedpresence-order.8849ms
location.updatedprivate-delivery.driver.driver-44.day-2026-05-2619ms
delivery.statusprivate-delivery.driver.driver-44.day-2026-05-2623ms
connectionclient → gateway
TCP handshake4ms
TLS negotiation18ms
WS upgrade22ms
App key validated26ms
Origin verified
Channel auth request
Subscribed
Receiving events

Architecture

The pieces developers wire together.

Client connectionBrowser, mobile, and desktop clients connect to the realtime gateway with a public app key.
Trusted originBrowser apps should connect only from approved origins configured for the realtime app.
Public channelsUse for non-sensitive live updates where any connected client can subscribe.
Private channelsUse signed server authorization before a user joins protected rooms.
Presence channelsUse private authorization plus member data when the UI needs online participants.
Server eventsPublish sensitive workflow decisions from trusted server code, not from the client.

SDK

Connect in any language.

quickstart.js
1color:#c084fc">const realtime = color:#c084fc">new color:#fde68a">DomViaRealtime({
2 key: color:#86efac">"pk_live_your_public_key",
3 host: color:#86efac">"ws.domvia.net",
4});
5 
6color:#c084fc">const channel = realtime.color:#fde68a">subscribe(color:#86efac">"private-chat.room.42");
7 
8channel.color:#fde68a">on(color:#86efac">"message.color:#c084fc">new", (event) => {
9 console.color:#fde68a">log(color:#86efac">"New message:", event);
10});
@domvia/realtimefull SDK guides →

Flow

From first app to production signal.

01

Create app

Create a realtime app in the console and keep one app per product environment.

02

Configure origin

Add production, staging, and preview origins deliberately. Remove old preview domains.

03

Connect client

Use the public key in the client and connect to the public realtime gateway.

04

Authorize private rooms

For private and presence channels, call your server route to validate the signed-in user.

05

Publish events

Trigger workflow updates from trusted server code and keep payloads small.

06

Observe

Use usage, status, denied traffic, and support signals to prepare for production traffic.

Workloads

Realtime patterns that map to real products.

MessagingChat rooms, typing indicators, read receipts, private support rooms, and inbox counters.
Banking alertsIn-app transaction activity, card activity, fraud review prompts, and approval state.
LogisticsDriver movement, dispatch boards, delivery checkpoints, route state, and control-room updates.
OperationsLive dashboards, incident panels, queue movement, usage counters, and admin updates.
AI workflowsStreaming responses, background job progress, moderation state, and document processing.
Mobile notificationsUse realtime while the app is open. Use push notifications for background or lock-screen delivery.

Docs

Where to go next.