Sanket.Chat

About Sanket.Chat

Why SANKET: A Sovereign Secure Communication Platform Built in India

SANKET (Sanket.Chat) by Tosh Defence is a sovereign secure communication platform for defence, government and other high-trust organisations. It combines end-to-end encrypted messaging, file exchange, voice and video calls and priority broadcast, built on Signal's independently audited libsignal and AES-256, with a depth of customer control that hosted messaging services are simply not built to offer: your infrastructure, your keys, your identity provider, your policies and your update timing.

What this means

The platform, in plain terms

Signal Protocol through Signal's official, independently audited libsignal library, with post-quantum PQXDH key agreement and the SPQR post-quantum ratchet

Server-blind by design: the server relays ciphertext and never holds the keys to messages, files, calls, reactions or encrypted broadcasts

One dedicated installation per organisation, on infrastructure you choose, from a sovereign cloud to a fully air-gapped network

AES-256 throughout: files, call media, local storage and transport, with AES-256-GCM-only TLS and hybrid post-quantum key exchange

Administrator FIDO2 security keys, signed device lists, device mutual TLS and hardware-backed keys on every phone

Your own identity provider (OIDC, SAML 2.0, LDAP), SCIM provisioning, your branding and your retention policy

No advertising model and no third-party analytics in any SANKET app or server

Server-blind by design

Privacy architecture

Privacy in SANKET is an architecture decision. Messages, files, calls, reactions and encrypted broadcasts are encrypted on the device, and the server relays ciphertext without ever holding the keys to read it. The routing information needed to deliver messages stays inside your own installation, and no SANKET app or server carries a third-party analytics or advertising SDK.

libsignal · Post-quantum · AES-256

Security model

SANKET is engineered on the assumption that networks and servers can be attacked. Content is end-to-end encrypted with libsignal, every approved device is bound by a hardware-backed key and its own client certificate, device lists are signed by the account's own devices so the server cannot silently add one, and releases are signed with freeze and rollback protection.

Hosted · On-premise · Air-gapped

Deployment control

Choose the operating model that fits your mission: Sanket.Chat, the free public app; Sanket.Work, a dedicated whitelabel installation hosted in any region on any cloud you choose; or Sanket.Enterprise, operated by you on-premise or fully air-gapped. The security design is the same in every edition.

No third-party analytics

No advertising model

SANKET has no advertising business model and no user profiling. No SANKET app or server contains a third-party analytics, advertising or crash-reporting SDK, and first-party usage counts stay inside the installation, where the organisation can switch them off.

Built on Signal's independently audited libsignal

Post-quantum protection for messages and transport

Server-blind: no keys to your content on the server

Cloud, on-premise and air-gapped deployment

Deployment path

Choose the right tier for your organisation

Sanket.Chat

Individual

The free private messaging app for iOS and Android, built in India and operated by Tosh Defence on Indian infrastructure.

Signal Protocol through libsignal
Post-quantum key agreement
Server-blind by design
No advertising or third-party analytics
Learn more

Sanket.Work

Organisation

A dedicated, whitelabel installation hosted in any region on any cloud you choose, operated for you under contract.

Same security design in every edition
Your branding
Administration console
Your own identity provider and SCIM
Desktop apps through your organisation
Hosted in the region you choose
Learn more

Sanket.Enterprise

Defence and Government

A customer-operated installation for defence, government and critical infrastructure, on-premise or fully air-gapped.

Same security design in every edition
On-premise or air-gapped
Your internal certificate authority
Offline licensing and signed offline updates
High availability with a second site
Dedicated support with SLA
Learn more
1

Move sensitive communication off consumer apps and foreign SaaS onto a platform your organisation owns and controls

2

Give administrators precise control over identities, devices, policies, retention and update timing

3

Present evaluators with a security architecture documented in a public whitepaper and built on independently analysed cryptography

Frequently asked questions

What is SANKET?

SANKET (Sanket.Chat) by Tosh Defence is a sovereign secure communication platform: end-to-end encrypted messaging, file exchange, voice and video calls and priority broadcast, built on Signal's independently audited libsignal and AES-256, deployed as a dedicated installation on infrastructure the organisation chooses, including air-gapped networks.

What makes SANKET different from Signal or WhatsApp?

SANKET uses the same Signal Protocol family through Signal's official libsignal library, and adds what organisations need: a dedicated installation, administrator control of identities and devices, your own identity provider, signed device lists, device mutual TLS, priority broadcast with acknowledgement, customer-defined classification labels and deployment from cloud to fully air-gapped.

Can SANKET run on our own infrastructure?

Yes. Sanket.Work is a dedicated installation hosted in any region on any cloud you choose, or on Tosh Defence hosting. Sanket.Enterprise runs on your own servers, connected or fully air-gapped, with your internal certificate authority, offline licensing and offline signed release packages.

Does SANKET use third-party analytics or advertising?

No. No SANKET app or server contains a third-party analytics, advertising or crash-reporting SDK. Installations include first-party, content-free usage counts that stay inside the installation, and the organisation can switch them off.

How are encryption keys managed?

Identity and session keys are generated on the device and protected by hardware-backed storage: the Secure Enclave on iOS, and StrongBox or the trusted execution environment on Android. The server never holds the private keys that would read messages, files or calls.

Start with a conversation, not a commitment

Tosh Defence works with security-conscious organisations through a structured evaluation. Tell us about your threat model and we will show you the right deployment path.