Sanket.Chat
The Problem

Sovereign Microsoft Teams Alternative for Sensitive Communication

SANKET is a sovereign alternative to Microsoft Teams for the conversations that matter most. Messaging, files and voice and video calls are end-to-end encrypted, the installation is dedicated to your organisation, and it can run in the region and on the cloud you choose, on your own servers or on a fully air-gapped network.

The SANKET Answer

End-to-end encryption for messages, files and calls

Dedicated installation under your control

Air-gap capable for closed networks

Focused, compact attack surface

See It In Action

The shift

Before SANKET vs. After SANKET

Before - current state risks

Sensitive conversations hosted on a suite whose service, keys and roadmap belong to a foreign provider

Server-side encryption, where the provider operates the keys to the content

Deployment options that stop short of closed and air-gapped networks

End-to-end encrypted messaging, files and voice and video calls, with the server blind to content

After - with SANKET

A dedicated installation in the region and on the cloud you choose, on-premise or air-gapped

Your own OIDC or SAML 2.0 identity provider for administrators, LDAP directory checks and SCIM 2.0 provisioning

A focused secure communication platform with a deliberately compact attack surface

Built for this

The architecture behind the solution

SANKET keeps sensitive conversations in an installation you control. Content is end-to-end encrypted on the device, the server never holds the keys to it, and no SANKET app or server sends telemetry to a third party.

Server-Blind Architecture

Collaboration suites typically encrypt on the server, where the provider operates the keys. SANKET encrypts end to end with libsignal and AES-256, so the server relays only ciphertext, and adds device client certificates, signed device lists and administrator security keys.

Signal Protocol via libsignal

Built on Signal's independently audited libsignal, with post-quantum PQXDH key agreement and the Double Ratchet with SPQR, so every message has a fresh key.

Administrator Control

Administrators control identities, groups, devices, policies and retention, with FIDO2 security keys protecting the console itself.

Sovereign Deployment

Use Sanket.Work for a dedicated hosted installation in any region on any cloud, or Sanket.Enterprise to operate the platform yourself on-premise or on a fully air-gapped network.

The result

What organisations achieve

Keep the most sensitive conversations on a platform under your own jurisdiction and control

Protect messages, files and calls with end-to-end encryption

Run secure communication on closed and air-gapped networks

Evaluation guide

Questions every buyer should ask

Does the platform encrypt messages, files and calls end to end rather than on the server?

Can it run in a region, on a cloud or on infrastructure that we choose?

Can it operate on air-gapped networks?

Can it use our own identity provider and directory?

Is the attack surface focused on secure communication?

Is it free of third-party telemetry?

FAQ

Frequently asked questions

What is the best Microsoft Teams alternative for sensitive communication?

For sensitive communication, look for three properties together: end-to-end encryption by default for messages, files and calls, an installation that runs on infrastructure you choose or operate, and no dependency on a foreign provider's cloud. SANKET combines all three.

Are Microsoft Teams chats end-to-end encrypted?

Teams encrypts chat messages in transit and at rest, with keys the provider manages, so the service itself can decrypt the content. End-to-end encryption in Teams is limited to some calls and meetings. SANKET encrypts every message, file and call end to end by default, and the server never holds the keys.

Does hosting Teams data in an EU or Indian region solve the sovereignty problem?

Data residency controls where data is stored, not who controls the service. A provider headquartered abroad stays subject to its home country's laws, such as the US CLOUD Act, wherever the data centre is. With SANKET the installation is dedicated to you and can run on infrastructure you operate.

Can SANKET run alongside Microsoft Teams?

Yes. Many organisations keep Teams for everyday collaboration and move sensitive conversations to SANKET - leadership, security, incident response and classified units. SANKET does not depend on Microsoft 365, so it also works as an out-of-band channel when Microsoft 365 is unavailable or compromised.

What is the key security difference between SANKET and Microsoft Teams?

SANKET encrypts messages, files and calls end to end on the user's device with Signal's libsignal and AES-256, and the server relays ciphertext without holding the keys. SANKET also runs as a dedicated installation that you can host where you choose or operate yourself.

Does SANKET include voice and video calls?

Yes. One-to-one and group voice and video calls run through the installation's own media server with AES-256-GCM frame encryption and SRTP AES-256-GCM, tuned for constrained links and able to work over HTTPS port 443.

Can SANKET run where Microsoft Teams cannot?

Yes. Sanket.Enterprise runs on fully air-gapped networks with an internal certificate authority, offline licensing and offline signed release packages.

Does SANKET replace document collaboration and project tools?

SANKET focuses on secure communication: messaging, file exchange, voice and video calls and priority broadcast. That focus keeps the attack surface compact, and it sits alongside the tools you already use for documents and projects.

Can SANKET use our identity systems?

Yes. Administrators can sign in through your own OIDC or SAML 2.0 identity provider, users can be checked against your LDAP directory and SCIM 2.0 provisions accounts.

Ready to solve this with SANKET?

Talk to the Tosh Defence team. We start with your threat model and deployment constraints - not a product pitch.