Before XEN
The infrastructure the brain runs on protects every organization's data alike, with no configuration on your side.
Your data lives replicated across several regions, encrypted in transit and at rest, protected at the network edge and backed up continuously. Inside your company, XEN decides who sees, who does and who approves.
The infrastructure the brain runs on protects every organization's data alike, with no configuration on your side.
XEN applies your roles: viewing, recording and approving are separate permissions per module and per person.
A 99.9 % availability commitment, a data processing agreement and documentary support in audits.
Replicas, protected edge, encryption, backups and point-in-time recovery.
Roles, permissions, action approval and a history of every decision.
99.9 % availability, a data processing agreement and audit support.
XEN runs on world-class infrastructure. These seven protections exist for every company from day one and depend on no configuration on your side.
Every write is copied to more than one geographic region. If a region fails, another one answers without your team noticing.
Traffic enters through a perimeter that absorbs denial-of-service attacks and filters malicious requests before they reach the brain.
Encryption in transit between your browser and XEN, and at rest in data and document storage.
Data is backed up continuously, not once a night, and the copies live apart from the operation.
The organization is restored to the minute before a mistake, without losing the rest of the day's work.
The network and its accesses are watched permanently; an anomaly is handled before it becomes an incident.
The scope of every query is resolved on the server from the session. No request crosses from one company to another.
Inherited security comes with written commitments for the organizations that need them.
Viewing, recording and approving are separate permissions, per module and per person. Agents work with the permissions of the person who authorizes them, never with permissions of their own.
An agent proposes, a person approves and XEN executes. The three steps stay in the history with who, when and on which document, and are read with each role's permissions.
In three different places, and none of them depends on the browser.
The session is verified on the server on every request; the scope comes from it, not from what the client declares.
Roles delimit what each person can view, record and approve in each module.
The actions that matter, whether an agent or a person proposes them, wait for whoever holds the approval permission.
Isolation, recovery, contract and history.