Madar Architecture & Principles
Madar is designed to solve a practical problem: people need private personal messaging and structured institutional collaboration on the same device without compromising either.
Design Philosophy
Clear visual hierarchy, calm notifications, and verifiable cryptographic boundaries between personal data and institutional records.
Engineering Model
Provide a single multi-vault application backed by independent servers, per-vault AES-256-GCM local databases, and Ed25519-signed runtime policies.
Core Principles
Clarity & Deference
Interfaces stay out of the way so people can focus on meaningful conversations and verified organizational decisions.
Verifiable Boundaries
Privacy and governance rely on cryptographic proofs—signed JWS policies, safety numbers, and wipe receipts—not assumptions.
Transparent Governance
When a workspace enables compliance archiving or DLP controls, the client displays a clear disclosure banner to the employee.
Technical Foundations
First-Frame WebSocket Auth
Access tokens never appear in URL query strings or proxy logs; authentication happens inside the initial WebSocket frame.
Zero-Knowledge Blind Push Relay
On-premise servers can wake mobile devices via a blind relay using opaque wake tokens without exposing sender identity or message content.
Bilingual RTL & LTR Craft
Built natively for Arabic (RTL) and English (LTR) across mobile, web, administrative console, and technical documentation.