Relay-Blind By Design
User-Owned Continuity
Server-Blind
Opaque relay boundary.
User-owned continuity.
The relay is not trusted with the conversation.
No hosted contact graph on the server.
Recovery stays yours, not ours.
Trust Boundary
Most communication tools centralize the structure around the conversation.
Xentrop removes that structure from relay authority.
Conventional Communication Stack
Hosted account graph, server-side membership, provider recovery.
Readable operational structure, channels, analytics, and relay-side assumptions that can become exposure.
Xentrop Boundary
Opaque relay, intentional contact establishment, user-owned recovery.
Storage-agnostic .xbk continuity, private environment onboarding, and a dedicated relay path for stronger operational isolation.
Review the architecturePlaintext → Opaque encrypted blob
Opaque By Default
Not just messages.
The surrounding structure matters.
Messages, call signals, profiles, media, and continuity data are designed around the same principle: reduce what infrastructure can learn, and keep sensitive recovery authority off the server.
.xbk continuity stays user-controlled and storage-agnostic. Profiles and media follow capability-bound access.
Architecture Moat
Xentrop is server-blind coordination infrastructure
The same blind boundary pattern applies across messages, call signals, profiles, media, recovery continuity, wakeups, and realtime transport paths.
Opaque Coordination Layer
Moves application-defined encrypted events without trusting relay infrastructure with plaintext content, plaintext type, routing meaning, or hosted recovery authority.
No Hosted Coordination Graph
Relationships, onboarding, and routing context are not maintained as a readable relay-side graph. Serious environments use signed onboarding and intentional establishment.
User-Owned .xbk Continuity
Encrypted, storage-agnostic backup and old-device transfer keep continuity under user or buyer control. Xentrop does not become the recovery authority.
Dedicated Coordination Boundary
Deployments can move toward operational isolation, jurisdiction choice, capacity control, stricter logging posture, and clearer trust-boundary ownership.
Threat Model Boundary
Honest privacy claims are part of the architecture.
Xentrop is designed so messages, call signals, profiles, media, wakeups, and realtime transport paths move through infrastructure as opaque encrypted coordination events. Residual network metadata is still stated plainly.
Read Security Boundary01
Outside Relay Authority
Plaintext content, plaintext type, coordination graph, private keys, and hosted recovery authority stay outside the relay boundary.
02
Still Observable
IP timing, opaque mailbox access, blob size, traffic volume, push timing, and call transport cadence can still exist.
03
Bounded Claim
Xentrop claims server-blind coordination infrastructure, not metadata-free or traffic-analysis-proof communication.
Product Proof
The client surface stays clear.
The boundary underneath is controlled.
Private Environment
Dedicated trust boundary
Environment, relay path, and onboarding posture can be separated for organizations that need operational isolation.
.xbk Continuity
Recovery stays user-owned
Identity and continuity can move through an encrypted backup file without making Xentrop the recovery authority.
Contact Establishment
No hosted contact graph
Relationships are established intentionally instead of being exposed as a readable production server-side graph.
Relay Exposure
A relay breach should not
become a conversation breach.
Relay compromise is still operationally serious. But Xentrop is designed so relay infrastructure does not hold plaintext messages, a hosted production contact graph, plaintext message-type headers, private keys, hosted recovery capsules, or .xbk passwords.
Residual network metadata remains: IP connection timing, opaque mailbox access, blob size, traffic volume, push timing where push is used, and call transport timing. Xentrop states those limits plainly.
Some teams cannot outsource
the shape of their communication graph.
The first environments are the ones where the pattern of coordination is already sensitive.
They need a controlled coordination boundary with honest operational assumptions.
Xentrop is built for environments where—the infrastructure around communication is part of the risk.
Availability
Android access channel is live
Questions
Frequently
Asked
Infrastructure, security boundary, deployment, and platform scope.
Xentrop is server-blind coordination infrastructure for organizations and environments where communication leakage is unacceptable. It combines a clear client surface with opaque payload movement, no production server-side contact graph, user-owned .xbk continuity, and private or dedicated deployment options.