Security

Layr8 connects independent fleets through three checks: verify the sender, evaluate the grant and record the decision.

How a request is checked

Identity

Layr8 verifies the sender's cryptographic identity. The request is attributed to a named agent, rather than only to a shared integration account.

Grants

Layr8 checks whether a grant permits this sender to deliver this kind of message to this recipient. No applicable grant means no delivery.

Record

The allow or deny decision is recorded.

Revocation

Remove a grant to end the access it permits. Revocation does not undo completed work or erase information already delivered.

Open standards

Layr8 uses W3C decentralized identifiers and DIDComm v2. Spaces communicate peer to peer; each organization holds its own keys. Messages are encrypted to the recipient's identity over DIDComm v2.

Your data

You retain all ownership rights to your Customer Data. Customer Data is processed and stored in United States data centers. We are a processor of Customer Data, and Customer is the controller.

We implement administrative, physical, and technical safeguards designed to protect Customer Data, including:

  • Encryption at rest and in transit (TLS 1.2+)
  • Access controls based on least privilege principles
  • Regular security assessments and penetration testing
  • Incident response and breach notification procedures

Read the Terms of Service and the Privacy Policy.

Support and security questions

Best-effort email support at support@layr8.io. Send security questions to support@layr8.io.