Trust · Security
Security
Solomon concentrates data that was previously scattered. That is what makes it useful, and what makes the security model the product.
01
Inside your perimeter
On-premise or your private cloud, single tenant, with your identity provider and your encryption keys. Customer data does not leave the deployment; the default configuration makes no outbound call carrying it.
02
Enforced by the backend
Every permission decision is made by the service that owns the data. The interface hides what you cannot do; it is never what stops you. Seven roles, plus per-user grants, row filters and field masking.
03
Complete audit trail
Every consequential action, every AI tool call and every export, in a table whose triggers refuse UPDATE and DELETE. Records carry identifiers and counts — never credentials, document content, or full account numbers.
What we do not claim
Solomon has not been independently penetration tested and is not certified against SOC 2, ISO 27001, PCI DSS or any other standard. Our current findings, fixes and residual risks are published in the repository rather than summarised into a badge.
See it on your data’s shape — not a slide deck.
A pilot runs on synthetic or masked data first, inside your perimeter.