Security
What actually protects your code and data — not aspirational marketing copy. Every claim below is backed by a specific, dated engineering decision.
Nothing leaves your network
LegacyLens runs entirely inside your own VPC or on-prem environment. There's no hosted service, no phone-home, no telemetry. Your source code and parsed metadata never reach us.
Every sandbox run is isolated
Generated code and original COBOL execute in a throwaway container with no network access, capped memory/CPU, a read-only filesystem, zero Linux capabilities, and a non-root user — never inside the application process.
Sessions can be revoked instantly
Disabling an account or signing out of all devices invalidates every already-issued session immediately, not just future logins.
SSO and self-service auth, your choice
Sign in with Okta, Azure AD, Ping, Auth0, or Keycloak via OIDC, or local email+password — and disable the local path entirely once SSO is your only sanctioned option.
Backups you can actually trust
Automated nightly backups with a restore procedure you can test on a schedule against a disposable database, without ever touching production.
A software bill of materials with every release
Every container image ships an SPDX-format SBOM, and every backend change passes a real, enforced vulnerability scan — not just an informational report.
Honest gaps
Not shipped yet — tracked, not hidden:
- • SAML (OIDC covers most enterprise identity providers today)
- • SCIM provisioning
- • Independent third-party certification (SOC 2 / ISO 27001)
Need the full technical detail?
Request access and we'll walk through the architecture, data flow, and deployment model directly.
Request access