Trust and security

Last updated: November 7, 2026

Enderis holds your agents, your evals and the records of your test runs. This page summarizes how we protect them. To learn what we store and how we use it, see How Enderis handles your data.

Data separation

Each workspace has its own database. Your agents, evals, playgrounds and runs are stored apart from those of every other workspace.

Access control

  • Organizations have four roles: owner, admin, editor and viewer.
  • Workspace admins can give editors and viewers a different role on a single workspace, or hide that workspace from them.
  • A service key acts on one workspace, with the editor or viewer role only.

Sign-in and credentials

  • People sign in with Google, with Microsoft, or with an email and a password. A self-hosted install uses the identity provider that you choose.
  • Sign-in credentials and API keys are stored as hashes.
  • Signing out ends the session on the server.

Encryption

  • Connections to the hosted service are encrypted in transit with HTTPS. Plain HTTP requests are redirected to HTTPS, and our website, web app and API tell browsers to use only HTTPS.
  • On the hosted service, the databases that hold customer data are encrypted at rest.
  • Secrets that Enderis must read later, such as a model endpoint key, are also encrypted by Enderis before they are stored.

Isolation of customer code

  • On the hosted service, customer code such as evaluators and simulated services runs in a sandbox, isolated from the service. The service does not start if its sandbox check fails.
  • A repository agent runs on your own machine. Enderis does not need your source code to run it.

Development and release

  • Every change to our main branch must pass our required automated checks.
  • Our build scans for exposed secrets and checks our dependencies for known vulnerabilities.
  • We scan each container image for self-hosted installs for vulnerabilities, then sign it and attach a signed software bill of materials.
  • The command-line tool checks a signature before it updates itself.

Self-hosted deployment

You can run all of Enderis in your own Kubernetes cluster, on your own database, with your own model gateway. With our default Helm chart, your data stays under your control and does not come to us. Contact us to discuss this option.

Security reviews and reports