Why we built it
Saj Link is built around two ideas: sovereign communications and on-device intelligence.
We started by listing every assumption baked into modern messaging — that work lives in Slack and life lives in WhatsApp, that you trust the server with plaintext, that you accept English as the default, that voice messages are second-class to text, that "Arabic support" means a translated UI on top of an English-first design — and we challenged each one.
The thesis
A new class of communication products will be defined by what they refuse to do: store your plaintext, send your audio off-device, force you into a single language, surveil your conversation patterns. The advantage of refusing isn't ideological — it's structural. A product that doesn't hold your data can't lose your data, and can't be the weak link.
What we ship
Saj Link's messages are end-to-end encrypted by default. A post-quantum protocol (Saj Protocol V2) is built and rolling out. Voice and video call audio is relayed through our servers today — not yet end-to-end encrypted. Voice transcription, translation, and search run on your device — your audio never leaves it. Arabic is a first-class language with native typography, true RTL, and dialect-aware STT covering MSA, Gulf, Egyptian, and Levantine.
What's next
Group voice calls via SFU (coming). Persistent voice channels (coming). QUIC transport (coming). On-device speaker identification (coming). Sovereign deployment with full architectural transparency for licensed customers — on-prem binaries, customer-controlled key management, audit rights — without exposing source or model weights under open-source licensing. Arabic developer documentation alongside English (coming).