Enclave

Where trusted conversations live.

Enterprise-grade encrypted communications embedded inside your app — workforce to workforce, customer to customer, and named relationship threads. One fabric, one identity, one deployment you control.

Request briefing → See architecture

Downloads Product Brief Executive Narrative

01 — Capabilities

Three conversation modes. One encrypted fabric.

01 / WORKFORCE

Staff-to-staff

Encrypted voice, video, and messaging between employees — replacing consumer messaging apps that regulators increasingly flag as a compliance risk for bank and government staff.

Voice & video calls
1:1 & group chat
File exchange
Retention & eDiscovery

02 / PEER-TO-PEER

Customer-to-customer

Encrypted conversations between customers inside your app — payment memos, referrals, family accounts, community banking. The social layer of a financial app, trusted by design.

Embedded SDK
Identity-bound contacts
Payment context
Per-message audit

03 / RELATIONSHIP

Client-to-banker

Persistent named threads between a client and their relationship manager. The thread is the franchise asset — it survives RM rotation, regulatory audit, and device change.

Persistent threads
RM rotation-safe
Audit-complete history
Voice notes & docs

04 / SUBSTRATE

Underlying fabric

All three modes share one identity, one policy engine, one telemetry stream. What your CISO audits once covers every conversation mode at once.

Unified identity
E2E encryption
Sovereign hosting
Policy-driven retention

02 — How it works

A message travels five gates before it's delivered — and every gate is yours, not ours.

Identity bindingTrust Platform · Per-device

Every participant — workforce, customer, RM — is bound to a platform identity tied to a Sentinel-attested device. No identity, no conversation. No attestation, no identity.

Registration

Mode-specific policyWorkforce / P2P / RM

Each of the three modes carries its own policy envelope — retention, eDiscovery access, allowed media types, disappearing-message rules. Policy is set once by the institution, enforced everywhere.

Pre-send

E2E encryptionDouble-ratchet · Per-message

Each message is encrypted end-to-end with a per-message key derived from a double-ratchet. The server routes ciphertext only. Nexilis, the host bank, and any intermediary see nothing readable.

Transport

Sovereign deliveryOn-prem · Private cloud

The message broker lives inside your trust boundary. No foreign SaaS hop, no data-residency exposure, no export-control risk. Your conversations never leave jurisdictions you control.

Routing

Auditable retentionCompliance · Immutable

Retention is a policy, not a product feature. Regulator-grade eDiscovery access for compliance; client-facing ephemerality when appropriate. Both governed by cryptographic proofs, not vendor promises.

Where Enclave earns its keep.

Priority & wealth banking

The RM thread as a franchise asset

Priority, wealth, and private banking clients who expect a direct line to their relationship manager — but where consumer messaging apps create unacceptable compliance exposure.

A named, persistent thread that survives RM rotation, satisfies OJK record-keeping, and feels as natural as WhatsApp to the client.

Defense · Government

Uniformed-service communications

Ministries, intelligence services, and defense commands where adversaries include nation-state actors, where consumer messaging is prohibited, and where sovereign hosting is a procurement requirement.

Workforce-grade encrypted comms with zero foreign dependency — auditable by your own security office, not by a vendor's SOC.

Community banking

Branchless agent banking networks

Agent banking networks — where the host bank reaches underserved regions through local agents — where trust between agents, customers, and the issuing bank lives in conversation — payment confirmations, beneficiary changes, dispute resolution.

Encrypted, identity-bound communications across the whole agent network — no WhatsApp, no unattributable disputes.

05 — Where it sits