Managed realtime chat & calls
Your database.
Your storage.
We run WebSocket delivery, sync, receipts, presence and WebRTC calls. Every message is written to your own PostgreSQL, MySQL or MongoDB, and files go straight to your bucket.
npm install byotalk- PostgreSQL · MySQL · MongoDB
- S3 · R2 · Azure · Cloudinary
- Free plan · 1,000 MAU
Sarah just now
Can we hop on a quick call about the invoice?
ByoTalk delivers in realtime then writes to your database
PostgreSQL
Your schema
MySQL · Mongo
Your tables
S3 · R2 · Azure
Your bucket
- Databases you can own
- 3
- Databases you can own
- Client SDKs
- 5
- Client SDKs
- Voice and video calls
- 1:1 + group
- Voice and video calls
- To start · 1,000 MAU
- $0
- To start · 1,000 MAU
Works with what you run
- PostgreSQL
- MySQL
- MariaDB
- MongoDB
- HTTPS endpoint
- Amazon S3
- Cloudflare R2
- Google Cloud Storage
- Azure Blob
- Cloudinary
- AWS KMS
How it works
We run realtime. You keep the record.
Three moving parts, and the permanent one is yours.
- 01
Your app connects
Web, React Native, iOS, Android and Flutter clients connect over WebSockets. We run delivery, ordering, sync after reconnect, receipts, typing and presence.
- 02
Messages reach your database
A replicator writes conversations, members and messages into your PostgreSQL, MySQL/MariaDB or MongoDB with a least-privilege writer, or posts signed batches to your HTTPS endpoint.
- 03
The record stays yours
Query, join and back up your chat history like any other table. We keep an encrypted copy of recent messages only to deliver, sync and retry.
Your web and mobile apps
byotalk SDK · WebSocket + WebRTC
Your backend
secret key · user tokens · REST
ByoTalk Infrastructure
Coremanaged · high-throughput · isolated
- gateway
- media (SFU)
- TURN
- push
- webhooks
- replicator
Your database
Postgres · MySQL · MongoDB · HTTPS
Your storage bucket
S3 · R2 · GCS · Azure · Cloudinary
Your webhooks
signed · retried · replayable
-- Your chat history is a table like any other
SELECT m.id, m.sender_id, u.email, m.text, m.created_at
FROM byotalk.messages m
JOIN app_users u ON u.id = m.sender_id
JOIN support_tickets t ON t.chat_id = m.conversation_id
WHERE t.status = 'escalated'
ORDER BY m.created_at DESC
LIMIT 5;- No API to page through. Read years of history with your own queries and indexes.
- Your backups. pg_dump, point-in-time recovery or snapshots, on your schedule.
- Nothing to export. If you leave, the tables are already in your database.
Our 100% Data Sovereignty Commitment
Your database is the permanent record of every message. We keep an encrypted copy of recent messages (7 days by default, down to 24 hours) to deliver, sync and retry, plus the IDs and memberships needed to route them. Encrypted backups of our database are kept for 7 days. Files go directly to your own storage when you connect it (otherwise to ours). Read how replication works →
Platform
Everything a chat product needs
Each of these is live today, with docs and tests behind it.
Realtime chat
Direct and group conversations with ordered delivery, sync after reconnect, read receipts, typing and presence.
Voice and video calls
1:1 and group calls with simulcast, screen sharing, ringing on every device and TURN relay.
Livestreams
Audience chat with a few hosts and any number of viewers, with a read-only mode.
Your own database
PostgreSQL 14+, MySQL 8+, MariaDB 10.6+, MongoDB 6+ or any store behind an HTTPS endpoint.
Your own storage
Attachments upload straight from the device to S3, Cloudflare R2, Google Cloud Storage, Azure Blob or Cloudinary.
Semantic search
Find messages by meaning with pgvector embeddings in your PostgreSQL, from an embedding model you choose.
Offline outbox
Sends wait in a local outbox and retry on reconnect; every send carries an id, so retries never duplicate.
Signed webhooks
Standard Webhooks signatures, retries with backoff for 72 hours, and replay from the dashboard.
Push notifications
FCM, APNs and Expo with your credentials; previews can show the text, only the sender, or nothing.
Your encryption key
Wrap each environment's data key with your own AWS KMS key; disable it and nobody can read our copy.
Analytics
Connections, messages, delivery latency, calls and webhook health per environment, with CSV export.
Isolation
Row-level isolation between environments, envelope encryption per environment and an SSRF-safe egress layer.
Voice & video
Calls inside every conversation
Start a call in any direct or group conversation. Signaling uses the chat connection you already have; media goes through our SFU, never through your backend.
- Ringing on every device, missed-call push, call history with end reasons
- Screen sharing, mute, camera switching, active speaker
- Simulcast: each viewer picks the quality of each tile
- Automatic reconnect and TURN relay for restrictive networks

- Default camera, configurable
- 720p
- Default camera, configurable
- Simulcast
- 3 layers
- Simulcast
- People per call
- Up to 50
- People per call
Bring your own storage
Files go straight to your bucket
Photos, videos and documents upload from the device to your bucket with short-lived presigned URLs. We check the upload, then link it to the message.
- Amazon S3, Cloudflare R2, Google Cloud Storage and other S3-compatible stores
- Azure Blob Storage and Cloudinary
- A connection test that checks upload, read, delete and browser CORS
- Hard-deleting a message removes its files too

- Storage providers
- 5
- Storage providers
- Direct uploads
- Presigned
- Direct uploads
- Bucket and bill
- Yours
- Bucket and bill
Livestreams
Chat for an audience
A livestream has a few hosts and any number of viewers. Viewers are not members, so they never fill your member lists, unread badges or push notifications.
- Viewers join with one call and chat alongside the hosts
- Read-only mode in one switch; hosts moderate any message
- Viewers rejoin and catch up automatically after a dropped connection
- History is replicated to your database like every conversation

- Viewer count
- Live
- Viewer count
- Sends per connection
- 10 / s
- Sends per connection
- Messages per channel
- Ordered
- Messages per channel
Semantic search
Search by meaning, in your database
Turn on search and new messages are embedded by the model you choose and stored with pgvector in your own PostgreSQL. Users only ever find conversations they belong to.
- Any OpenAI-compatible embeddings API, including self-hosted Ollama or vLLM
- Embeddings live only in your database, next to the messages
- chat.search() in the SDK and POST /v1/search for your server
- Edits re-embed, deletes remove the vector

- In your PostgreSQL
- pgvector
- In your PostgreSQL
- Your provider
- Your model
- Your provider
- Only their chats
- Members
- Only their chats
SDKs
Native on every platform
One protocol, five client SDKs with the same model: conversations, an ordered message store, an offline outbox and sync after reconnect.
- TypeScript for web and Node (about 10 KB gzipped core, no dependencies)
- React Native with MMKV or AsyncStorage persistence
- Swift for iOS and macOS, Kotlin for Android and the JVM, Dart for Flutter
- Calls in the web and React Native SDKs

- Client SDKs
- 5
- Client SDKs
- Server SDK (Node)
- 1
- Server SDK (Node)
- Errors and events
- Typed
- Errors and events
Developers
First message in minutes
Install the SDK, mint a token on your server, connect. Development environments accept dev tokens, so you can start without a backend.
npm install byotalkimport { Chat } from "byotalk";
import { CallClient } from "byotalk/calls";
const chat = new Chat({
env: "env_…",
token: () => fetch("/api/chat-token").then((r) => r.json()).then((d) => d.token),
});
await chat.connect();
// Direct conversation, live updates, offline-safe send
const dm = await chat.conversations.direct("bob");
dm.on("message.new", (m) => console.log(m.senderId, m.text));
await dm.send({ text: "The invoice is ready" });
// Video call in the same conversation
const calls = new CallClient(chat);
const call = await calls.start(dm.id, { video: true });Compare
Same realtime, different owner
Hosted chat APIs run delivery and keep the record. ByoTalk runs delivery; the record is yours from the first message.
| Typical hosted chat API | ByoTalk | |
|---|---|---|
| Permanent message record | In the vendor's database; you export it through their API | In your PostgreSQL, MySQL, MongoDB or HTTPS endpoint |
| What the vendor keeps | Full history, for as long as you stay | An encrypted copy of recent messages (7 days by default, down to 24 h) for delivery and sync |
| Joining chat with your data | Through API calls and webhooks | Plain SQL / queries on your own tables |
| Attachments | In the vendor's storage | Uploaded straight to your S3, R2, GCS, Azure or Cloudinary |
| Encryption key for vendor-held data | The vendor's | Ours by default, or your own AWS KMS key |
| Leaving | Export, transform, re-import | Remove the SDK; the tables are already yours |
Use cases
Built for products that own their data
The same SDK and APIs, shaped by what you are building.
Support and marketplaces
Buyers, sellers, drivers and agents chat and call inside your app; the conversations sit next to your orders and tickets.
- Join chats with orders in SQL
- Calls with ringing and missed-call push
- Webhooks into your support tools
Health and regulated teams
Keep the permanent record in a database you already govern, and hold the key to what we keep for delivery.
- Record in your own database
- Your AWS KMS key for our buffer
- Push previews that never show message text
Communities and live events
A few hosts, any number of viewers: livestream chat with read-only mode, next to group chats and DMs.
- Livestream channels
- Presence, typing and receipts in groups
- History replicated like any chat
AI assistants
Search conversations by meaning with embeddings stored in your own PostgreSQL, from a provider you choose.
- pgvector in your database
- OpenAI-compatible or self-hosted models
- Members only ever find their own chats
Pricing
Simple, per active user
Free to start, including production. Development environments are always free.
Free
- ✓1,000 monthly active users
- ✓100 peak connections
- ✓4 people per call
- ✓Overage: Hard cap
- ✓Community; production use allowed
Starter
- ✓2,500 monthly active users
- ✓250 peak connections
- ✓8 people per call
- ✓Overage: $0.02/MAU
Growth
Popular- ✓10,000 monthly active users
- ✓1,000 peak connections
- ✓16 people per call
- ✓Overage: $0.018/MAU
Scale
- ✓50,000 monthly active users
- ✓5,000 peak connections
- ✓32 people per call
- ✓Overage: $0.015/MAU
- ✓Priority
Need custom volume or a DPA? Contact Enterprise Sales →
Detailed Plan Comparison
| Plan | Price | MAU | Peak Connections | People per Call | Overage | Support |
|---|---|---|---|---|---|---|
| Free | $0 | 1,000 | 100 | 4 | Hard cap | Community; production use allowed |
| Starter | $49/mo | 2,500 | 250 | 8 | $0.02/MAU | |
| Growth | $199/mo | 10,000 | 1,000 | 16 | $0.018/MAU | |
| Scale | $599/mo | 50,000 | 5,000 | 32 | $0.015/MAU | Priority |
| Enterprise | Custom | Custom | 5% of MAU | 50 | Custom | Custom DPA, dedicated support |
- Do you store our messages or recordings permanently?
- Your database is the permanent record of every message. We keep an encrypted copy of recent messages (7 days by default, down to 24 hours) to deliver, sync and retry, plus the IDs and memberships needed to route them. Encrypted backups of our database are kept for 7 days. Files go directly to your own storage when you connect it (otherwise to ours).
- Which databases can hold the record?
- PostgreSQL 14+, MySQL 8+ / MariaDB 10.6+ and MongoDB 6+ natively. For anything else, point us at an HTTPS endpoint: we send signed batches and you write them wherever you like.
- What happens if we leave ByoTalk?
- Your database already holds every conversation, member and message. Remove the SDK and keep your tables; there is nothing to export.
- Are calls recorded?
- No. Calls run on our media servers, encrypted in transit (DTLS-SRTP), and we never record audio or video. Call start and end reach your backend as signed webhooks.
- Can we hold the encryption key?
- Yes. Wrap your environment's data key with your own AWS KMS key. Disable the key and nobody, including us, can read what we keep for delivery.
- How is delivery guaranteed?
- At-least-once delivery with automatic de-duplication: every send carries a client id, so retries never create duplicates.
- What counts as a monthly active user?
- A distinct user ID that connected or sent a message in the month, in production environments only. Development environments are free.
Start with the free plan
Sign in with your email, create an app, and send your first message from the browser playground before you write any code.