Isolation by architecture
Every instance runs with its own private data store and its own identity space (nexp IAM). Tenants never share tables, credentials or sessions — isolation is structural, not a configuration flag.
Access control, end to end
- Identity. Every request is authenticated by nexp IAM (OpenID Connect); SSO and brute-force protection are built in.
- Permissions. App access, roles and groups gate what a user can reach — in the UI and the API alike.
- Data policies. Column- and row-level rules are enforced server-side on every query; what a user cannot see never leaves the server.
Platform practices
- TLS for all traffic; encrypted backups before any archive step.
- Server-side execution of application logic — server functions and widget data sources never ship to the browser.
- Signed licenses and authenticated agents in the control plane.
- Audit logging for administrative and lifecycle operations.
Responsible disclosure
We welcome reports from security researchers. Send details to [email protected]— we acknowledge every report and keep you informed while we investigate. Please avoid accessing other tenants' data or degrading the service while testing.
Questions
Enterprise security questionnaires and compliance documentation are handled by [email protected].