Direct messages and groups
Real-time sync across devices. Send photos, videos, voice, files and locations. Schedule messages and the server delivers them on time.
Multi-tenant instant messaging
Tenet gives every tenant its own data plane, its own apps and its own console. Desktop, web, iOS and Android share one backend, with chats, channels, bots, customer service and calls built in.
Available on
Features
A Telegram-class chat experience, plus the consoles, bots and customer service a business needs.
Real-time sync across devices. Send photos, videos, voice, files and locations. Schedule messages and the server delivers them on time.
Broadcast to many people. Only the owner and admins can post, and the server checks this both when sending and at scheduled delivery.
Any user can create a bot and receive messages by long polling or webhook, with command menus and inline buttons.
Invite agents and they serve the customers of your app from the Tenet desktop app. Customer data always stays in your own data plane.
One-to-one and group calls. The media server is deployed with the data plane, so calls never pass through a third-party platform.
The platform manages tenants in the admin console. Tenants manage apps, push, SMS and e-mail settings in their own console; secrets are stored encrypted and are write-only.
Security
WSS is only the carrier. Tenet adds an application-layer encryption on top of it that protects every frame, including sign-in credentials and tokens. When you need more, start an end-to-end encrypted one-to-one Secret Chat.
X25519 key exchange, an Ed25519 server signature, and HKDF-SHA-256 deriving separate AES-256-GCM keys for each direction. Replayed, reordered or tampered frames are rejected.
To provide multi-device sync, search, moderation and offline delivery, the server can read regular chats.
Groups, channels, customer service, bots, and conversations you want with full history on every device.
Starts only after the other person accepts. Message keys move forward and old keys are erased; a fresh key exchange is required after 100 messages or seven days.
Both devices show the same fingerprint. Verification is your explicit choice and is never assumed just because decryption worked.
The server sees only the size of the ciphertext, not the image, the file name or the file type.
End-to-end encryption currently covers one-to-one Secret Chats only, not groups. The protocol has not yet had an independent third-party security audit.
Tenant isolation
We do not isolate tenants by adding a tenant filter to every query, where one missed filter could leak data across tenants. Each tenant has its own database, cache, message queue, object storage, signing keys, network and backups.
On connect, the tenant configured on the data plane must match the tenant signed in the encrypted handshake, or the connection is refused.
No storage, network or authentication authority is shared between data planes.
Operations
Servers only pull released images and check each one by its digest.
A new version must pass health checks in isolation before any traffic moves.
When the database changes, a backup is taken first and every step is logged.
One side is replaced at a time. If any step fails, the previous version is restored.
Developers
The web SDK, native SDKs and the Bot API are fully documented. Every client connects to a single endpoint, /apiws, and never receives a server API key.
curl https://api.tenet.im/bot/$TOKEN/sendMessage \
-H 'Content-Type: application/json' \
-d '{
"chat_id": "g10086",
"text": "Daily check finished. All healthy.",
"reply_markup": {
"inline_keyboard": [[
{"text": "View report", "callback_data": "report"}
]]
}
}'
Tell us how you plan to use it, and we will help you set up your tenant and app.