Security at Leanroute

What we protect, and how.

You're trusting Leanroute with API keys, prompts, and billing data. The short version: Singapore-hosted, TLS 1.2+ everywhere, BYOK keys encrypted with a master held only in runtime memory, per-org cache isolation, monthly automated security scans, and an active disclosure channel. The long version — regulatory regimes, sub-processors, controls — lives on /compliance.

Reporting a vulnerability

Please report suspected security issues to support@leanroute.dev. We acknowledge within one business day and target a triage decision within five. PGP is available on request.

We commit to safe-harbor for good-faith research that respects our disclosure policy: no denial-of-service, no data exfiltration beyond proof-of-concept, no accessing other customers' data, and give us reasonable time to fix before public disclosure (default 90 days).

Formal reference: /.well-known/security.txt (RFC 9116).

Certifications & attestations

Leanroute is not currently SOC 2, ISO 27001, or HIPAA-attested, and we don't display badges we don't hold. If your procurement needs more, we can complete a security questionnaire (SIG Lite / CAIQ) and sign a DPA with Standard Contractual Clauses.

AttestationStatus
SOC 2 / ISO 27001
Not yet
Not attested. We answer security questionnaires (SIG Lite / CAIQ) and sign a DPA in the meantime.
PDPA (Singapore)
Aligned at launch
Data residency in Singapore. See /compliance for details.

Security testing

How we test, and how often:

Automated security scanning
Monthly · 2 rounds completed

Dynamic scans of the live site and API with OWASP ZAP, run every month. Two rounds completed since September 2026; findings from the first round led to the security-header baseline now in place. Customers can request the latest scan report at support@leanroute.dev.

Coordinated disclosure program
Planned — post-launch

Public program on HackerOne or Intigriti with a modest bounty pool. Timeline: within 90 days of GA.

Continuous automated review
Live

Dependabot on every repo, secret scanning enabled, npm audit on CI, Semgrep on pull requests.

What's in place today

TLS 1.2+ end-to-end

Every hop encrypted — browser to gateway, gateway to every upstream provider, internal service to service.

BYOK keys encrypted

Provider keys wrapped with AES-256-GCM under a runtime-only master. A leaked DB dump is useless without the master.

Per-org cache isolation

Cache keys namespaced by org id — a hit from one org can't satisfy a request from another. No cross-tenant leakage path.

Hard spend + rate caps

Daily and monthly spend caps + per-key RPM/TPM throttling. Runaway loops hit the wall before an upstream call is made.

Monthly security scans

Automated scans of the live site and API with OWASP ZAP every month. Findings are tracked and re-checked on the next run. Report available on request.

Full control list, sub-processors, and residency detail on /compliance.

Enterprise procurement

We handle security questionnaires (SIG Lite / CAIQ), sign DPAs with EU Standard Contractual Clauses, and can walk you through the request-flow diagram on a call. Email sales@leanroute.dev with what you need — response within one business day.

support@leanroute.devCompliance posturePrivacy policyTermssecurity.txt