Getting started
GuideConnect your first realtime app
This is the safest first path for connecting a new app. Create the app, trust your website origin, use the public key on the client, and keep private authorization inside trusted server code.
Public documentation
Build realtime apps with confidence.
Learn how DomVia Realtime apps, keys, origins, channels, usage limits, gateway status, and security events fit together. Start small, protect sensitive flows, then scale into production operations.
Create your first realtime app, add trusted origins, copy your public key, and connect your client.
Understand how apps, regions, environments, limits, endpoints, and app IDs work together.
Learn the difference between public keys, secret keys, secret previews, and safe rotation.
Protect realtime traffic with trusted origins, signed channel authorization, usage limits, and alerts.
Start here
SDK guides
GuideModular packages for chat, location, delivery, calls, and private encryption.
Keep the public docs clean. Each SDK guide gives a short preview here, then opens into a focused full page when the developer wants implementation depth.
Core concepts
Apps
GuideHow realtime apps are organized
A realtime app is the main container for credentials, origins, channel access, limits, and environment settings.
Credentials
GuidePublic keys, secret keys, and rotation
Keys are the most important part of your setup. Public keys identify apps. Secret keys sign protected actions and must stay private.
Realtime channels
GuidePublic, private, and presence channels
Channels are realtime rooms. Choose the right channel type based on whether the data is public, protected, or needs online member visibility.
Production safety
GuideSecurity is a workflow, not one switch
Security is not one switch. It is a full workflow: safe keys, trusted origins, signed private access, usage limits, security events, and alerts.
Reference
Fix issues faster
GuideCommon realtime problems and fixes
Most realtime issues come from wrong keys, blocked origins, missing channel authorization, or usage limits.
Reference
GuideCommon API areas
These are the main API areas your console uses. Protected workspace endpoints require an authenticated console token.
SDK guides
@domvia/realtime-chat
SDKPrivate chat rooms
Model room messages, typing state, read receipts, presence, and encrypted payload decisions without turning the core SDK into a messy all-in-one package.
@domvia/realtime-location
SDKLive location streams
Send controlled, short-lived location updates for trips, same-day deliveries, inspectors, drivers, couriers, and field workers.
@domvia/realtime-delivery
SDKDelivery timelines
Track pickup, in-transit, nearby, delivered, failed, and support-needed states with realtime visibility for customer and operator screens.
@domvia/realtime-calls
SDKIn-app call signaling
Coordinate WhatsApp-like audio and video call state with ringing, accept, reject, end, WebRTC offer, answer, ICE candidate, and media state events.
@domvia/realtime-e2ee
SDKStrong privacy mode
Encrypt sensitive JSON payloads for private chat, call signaling, live location, delivery notes, and custom private events when protected channels alone are not enough.