Stance
Trust
We build trust through design decisions. This page is the summary of those decisions, and where a security note should go.
What we build
01
Least privilege
Access stays narrow. Broad access is justified.
02
Auditability
A critical action leaves a trail. Who, when, and what does not go unanswered.
03
Secrets
Keys and credentials do not live in code. They sit in a managed secrets layer.
04
Continuity
Monitoring, alerts, and recovery are part of the product. The work does not stop when the office day ends.
Boundary
A product account, subscription, and customer data follow that product site’s rules. This page is the company’s stance.
Documents
A compliance document will sit here when one is published.
If you see a weakness, write to us first. The topic arrives as security.
Write a security note