Trust, engineered in.
These are the controls an institution audits before it moves a dollar — ledger integrity, encryption, a compliance program, and the access discipline your reviewers expect. And the same infrastructure ships the uptime a builder counts on without thinking about it.
What holds when value moves.
Four guarantees underwrite every movement on the platform. Each is enforced in code, not promised in prose — and each is auditable to the entry.
Append-only, and balanced by construction.
The ledger is double-entry and append-only: entries are written, never edited or deleted. Debits must equal credits — enforced in the database and again in the service layer — so an unbalanced transaction cannot post. Balances are derived from entries, never stored, which means every figure reconciles to the cent and the timestamp that produced it.
- Append-only entries
- Debits == credits, in SQL and service
- Balances derived, never stored
- Auditable to the individual entry
- Model
- Double-entry, append-only journal.
- Invariant
- Sum of debits equals sum of credits on every transaction.
- Enforced
- Database constraints and the service layer, independently.
- Balances
- Computed from entries on read — not mutated in place.
Encrypted in transit, encrypted at rest.
Traffic is encrypted in transit, and data is encrypted at rest. Keys are managed centrally with rotation and scoped access, secrets are held in a managed store rather than in code or configuration, and access follows least privilege. Tenants are isolated so one customer's data is never reachable from another's context.
- TLS in transit, encryption at rest
- Centralized key management and rotation
- Least-privilege access
- Tenant isolation by design
- In transit
- TLS across all external and service-to-service traffic.
- At rest
- Encrypted storage with managed, rotated keys.
- Secrets
- Held in a managed secrets store, scoped per service.
- Isolation
- Per-tenant boundaries on data and access paths.
Screened at onboarding, and on every movement.
KYC, KYB, and AML run at onboarding through regulated partners, and real-time sanctions screening evaluates counterparties before value leaves an account. Travel Rule information is exchanged where required. Every decision and movement lands in an immutable audit log — the same record your regulators and ours both read.
- KYC, KYB, AML at onboarding
- Real-time sanctions screening
- Travel Rule where required
- Immutable audit log
- Onboarding
- KYC / KYB / AML via regulated partners.
- Screening
- Sanctions checks in real time, before a movement clears.
- Travel Rule
- Originator and beneficiary data exchanged where mandated.
- Audit log
- Append-only record of every decision and entry.
Who can act, what gets approved, what can be replayed.
Role-based access governs who can act, and approval workflows gate the actions that warrant a second pair of eyes. Webhooks are signed and replayable, so an integration can verify authenticity and recover missed events deterministically. The platform is engineered for 99.99% settlement uptime — built for continuous settlement, not best-effort.
- Role-based access control
- Approval workflows on sensitive actions
- Signed, replayable webhooks
- Engineered for 99.99% settlement uptime
- Access
- Role-based permissions, least privilege by default.
- Approvals
- Multi-party workflows on sensitive operations.
- Webhooks
- Signed for authenticity, replayable for recovery.
- Uptime
- Engineered for 99.99% settlement availability.
Independently attested.
The frameworks institutions ask for, maintained and evidenced through audited partners where applicable.
- SOC 2 Type II
- PCI DSS
- ISO 27001
- GDPR
Certifications are maintained through audited partner institutions and licensed entities where applicable. Current attestations and reports are available to customers and prospects under review.
Found something? Tell us.
If you believe you have discovered a vulnerability in our systems, we want to hear from you. Report it privately and give us a reasonable window to investigate and remediate before any public discussion.
How to reach us
Send a clear, reproducible report — affected endpoint, steps, and impact. Encrypt sensitive details with our published PGP key, available on request.
Safe harbor: research conducted in good faith and in accordance with this policy — without privacy violations, data destruction, or service degradation — will not be pursued by AUREUS, and we will work with you in good faith to resolve issues promptly.
Answers, plainly.
Data is stored in the regions our infrastructure and regulated partners operate in. Where a specific data-residency requirement applies, we scope it during onboarding and confirm what can be supported for your jurisdiction before you go live.
Yes. The platform is tested by independent third parties on a recurring basis, and we run continuous internal review alongside it. Summaries and current reports are available to customers and prospects under review.
We maintain a defined incident-response process with on-call ownership, severity classification, and customer notification through regulated partners where applicable. Material incidents are communicated to affected customers without undue delay, with remediation and follow-up.
Banking, payment, and custody services are delivered through regulated partner institutions, and a small set of infrastructure subprocessors supports the platform. A current list, with the function each performs, is provided under review and updated as it changes.
No. The ledger is append-only — entries are never edited or deleted, and corrections are themselves new, balanced entries. Because balances are derived from history rather than stored, the record cannot be quietly rewritten, and every figure remains auditable to the entry that produced it.
Move value on infrastructure you can audit.
Walk our controls with your security and compliance teams, then build on the same ledger they reviewed.