Platform

Security described precisely, including what is not built yet

Tenant isolation, role enforcement at the service boundary, audit logging and a signing boundary — stated as designed architecture, not as marketing.

Problem

Security pages are usually written to reassure, not to inform

Vague absolutes — unhackable, fully quantum-proof, military-grade — tell a technical buyer nothing, and they age badly the moment someone asks a specific question.

A business handing over customer identity and balances needs to know exactly where the boundaries are, what is enforced today, and what is on the roadmap.

Solution

A boundary you can point at

Every request is authorized against an identity, an organization and an environment. Network position grants nothing; an internal service call is authenticated the same way an external one is.

Key material sits behind a signing boundary that application code never crosses. Privileged actions are recorded with actor, target, environment and result, whether the actor was a person, a service or an AI agent.

Posture

Capability by capability

Tenant isolation

Planned

Every record belongs to exactly one organization; queries are scoped at the boundary rather than by convention.

Role enforcement

Planned

Permission checks run in the service layer, not the interface, so an API call faces the same rules as a click.

Environment separation

Planned

Test and production data and credentials are fully separate. A test action cannot reach a production wallet.

Signing boundary

Planned

Private key material is never returned by an API and never enters customer application code.

Audit logging

Planned

Privileged actions recorded with actor, target, environment, result and request ID.

Cryptographic agility

Planned

Signing schemes and key material are versioned so algorithms can be migrated — including to post-quantum algorithms — without re-issuing customer wallets.

Practice

How we talk about security

No absolutes

We do not describe anything as unhackable or fully quantum-proof. Those claims are not supportable.

Planned is labelled

Capabilities under development are marked planned wherever they appear.

No borrowed trust

We do not display certifications we do not hold or customers we do not have.

Specific answers

Enterprise security questions get a written answer about the actual implementation.

Reviewing us for an enterprise deployment?

Security questionnaires get a direct written response about what is implemented today and what is scheduled.