How does BetterSuite approach security and operational trust?

Authentication is passkey-first, with email verification codes as the fallback. Operator and admin roles are scoped per service — a regional support agent cannot access financial reconciliation, and a marketplace operator cannot touch platform infrastructure settings.

All sensitive actions are written to a tamper-evident audit log that retains origin metadata, the actor, and a structured event payload.

Data is encrypted in transit with TLS and at rest with managed keys. Payment service provider credentials are stored encrypted with a per-operator envelope key, and the encryption layer is rotated independently of the application runtime.

Personally identifiable information is segregated from operational tables and only joined at the API boundary when access is authorized.

Reliability is a product feature. Every service emits structured logs, traces, and metrics, and a built-in dashboard surfaces system health to operators in real time. Releases are versioned, signed, and reversible.