01The self-hosted model
The whole system — gateway, optimizer, console, and Postgres (the spend and trace store) — runs inside your cloud account. The only data that egresses is a content-free usage rollup for metering: counts, aggregates, and pseudonymous seat hashes, never prompt or response content.
This inverts the usual vendor trust boundary. You operate the software; your data stays with you. There is no vendor-side store of your content to breach, and no new vendor in your data path.
02How the software is secured
- Access control. The console and every
/adminroute sit behind a single admin key; the developer-facing/v1surface uses per-developer credentials issued through passwordless, public-key enrollment — no shared secret and no SSO requirement. - Credential handling. Provider API keys are held server-side, never returned to a caller, and audit-logged by provider slug only — never the value.
- Abuse & DoS controls. Built-in per-key and per-IP rate limits, concurrency caps, body-size limits, and a brute-force brake on the gateway.
- Transport security. The gateway sits behind a TLS edge. Traffic is redirected by base URL — there is no org CA, no TLS-MITM, and no proxy on developer machines.
- Update integrity. Image updates run through a least-privilege, read-only Docker socket proxy, scoped to Anyray containers, admin-gated and opt-in — with no inbound access to your environment.
Operational detail. The control mechanics, environment variables, and endpoints behind each of these live in the product documentation at docs.anyray.ai/operate/security.
03Detailed practices
Each area below has its own page, written for a security reviewer working through a due-diligence questionnaire.
- Data ProtectionThe data boundary, encryption, what egresses, retention, and data-subject rights.
- ComplianceController/processor roles, the shared-responsibility split, audit trails, and standing.
- Risk AssessmentThe assessment practice, cadence, and article-by-article regulatory standing.
- Asset InventoryEvery data store, secret, and service — classified, with an owner and a location.
- SubprocessorsWho processes what — and why nothing in the data path is a subprocessor.
- Vulnerability DisclosureHow to report a vulnerability, and our software supply-chain integrity.
04Certifications & assurance
Anyray holds its own SOC 2 Type II attestation. And because the software runs in your environment, the attestation program for your deployment stays yours — Anyray supplies the control inventory and audit evidence to support it. Regulatory standing is detailed article by article on Risk Assessment.
Anyray holds a SOC 2 Type II attestation of its own program (observation period 4 July – 4 October 2026), independently examined by Securance Pro Assurance PLLC against the Security, Availability, Confidentiality, and Privacy Trust Services Criteria with no exceptions noted; the report is available under NDA and downloads instantly from the Trust Center. It follows the SOC 2 Type I attestation of 6 July 2026. The last penetration test, an external grey-box assessment of the staging environment, was completed in August 2026 with no critical, high, medium, or low severity findings; the report is available under the same NDA.
The one thing Anyray operates — the content-free metering/Billing App backend — runs on AWS in the EU (Frankfurt): private-subnet compute behind a web application firewall, encryption in transit (TLS 1.2/1.3, including between services inside the production network) and at rest (AES-256, AWS KMS), continuous threat detection and vulnerability scanning (GuardDuty, Inspector, Security Hub, AWS Config), and least-privilege access. It never receives prompt or response content.
05Contact
Email: security@anyray.ai