Docs
ByoTalk documentation
Managed realtime chat and calls whose permanent record lives in your own 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 →
- Quick startFirst realtime message in six lines; production token route.
- iOS and SwiftSwift Package for iOS and macOS: tokens, conversations, offline sends.
- Android and KotlinKotlin SDK for Android and the JVM, with coroutines and Flow.
- Flutter and DartChat in Flutter and Dart apps: install, tokens, lifecycle, offline sends.
- Bring your own databasePostgreSQL, MySQL/MariaDB, MongoDB or an HTTP endpoint as the permanent record.
- HTTP endpoint (any database)The ping, batch and read contract for any other database.
- Media storageCloudinary, S3-compatible buckets or Azure Blob, and CORS rules.
- Semantic searchSearch messages by meaning: embeddings in your PostgreSQL, any OpenAI-compatible provider.
- LivestreamsAudience chat: a few hosts, any number of viewers, history in your database.
- Voice and video calls1:1 and group calls with the SDK, moderation, webhooks and push.
- Encryption keys (AWS KMS)Wrap your environment's data key with your own AWS KMS key.
- Data location statementWhat we keep, where, and for how long.
- REST API overviewAuthentication, errors, pagination, resources.
- Realtime protocolWebSocket frames, sync, reconnection, presence.
- WebhooksEvent catalogue, delivery rules, signature verification.