Enterprise data security
Contracted enterprises can review data handling, failover and model channels before integration.
Checks database connectivity and queue load.
How we protect data
Credential protectionHashed enterprise keys, encrypted upstream credentials
- Enterprise API keys
- The server stores SHA-256 hashes. Full keys are shown when issued. Enterprises can disable or delete them.
- Upstream credentials
- Channel credentials are stored with AES-256-GCM encryption. The gateway provides a root-key rotation command.
- Sign-in and sessions
- Passwords are hashed with Argon2. Changing a password or removing a member revokes the associated sessions.
Tenant isolationResources scoped by tenant, access based on roles
- Tenant scope
- Enterprise queries are scoped to the session’s tenant. The gateway checks ownership when a record is requested.
- Member permissions
- Roles control management and finance actions. The server checks the caller’s identity and permissions.
- Access and rate limits
- API keys support access scopes, request limits and IP rules. The management console uses same-origin access by default.
Requests and audit recordsCapture off by default, usage traceable by request
- Request handling and capture
- Request bodies are sent to the selected upstream model service to fulfill the call. Gateway capture for troubleshooting is off by default. When enabled, captured content is encrypted with AES-256-GCM and deleted according to the configured retention period.
- Usage and billing
- The platform records model, usage, latency, status and charges. Pricing snapshots are stored with settlements and can be traced by request ID.
- Audit trail
- Enterprise administrators can review member, key and quota changes within their permissions. Audit records are also available to authorized platform administrators.
Service continuity controls
Applicable service levels and support are set out in the enterprise agreement.
Layered rate limits
Apply request and usage limits by enterprise, API key and channel to manage traffic spikes.
Failure isolation
Repeated failures can trip a circuit breaker and temporarily take that route out of rotation.
Backup routing
When a request is eligible for retry and a backup channel is available, the gateway can try an alternate route.
Model channels and selection
For public-cloud routes, we evaluate official APIs from model makers and official model services from cloud providers. Private inference nodes can be integrated as agreed. Available routes, regions and terms depend on your contract and deployment.
Official model APIs
Review the API source, model version and applicable conditions.
Official cloud model services
Review channel authorization, service regions and data processing terms.
Model makers listed in the public catalog
Loading the catalog…
