LIVECT
Network & Security Architecture
Public, IP-allowlisted and private network modes, credential separation and request controls.
Public endpoint
Base access mode to the agreed API endpoint.
Client→Internet→AI Gate
IP allowlist
Public endpoint restricted to corporate source IPs for API and/or login.
Corp IP→Allowlist→AI Gate
VPN / private network
Closed access through site-to-site VPN / private network.
Corp network→VPN→AI Gate
Request path
Access controls before upstream routing
ClientModel API key
→
Auth & policykey · user · project · IP
→
LimitsRPM · concurrency · spend
→
Routingmodel / upstream
→
Providerexternal endpoint
Credential separation
Model API key is used for inference. Partner token is for trusted server-to-server management.
Corporate access
Roles, project permissions, mandatory 2FA and IP policies.
Partner token storage
Hash-only; the full secret is shown on generation/rotation.
Health model
/health/live checks the process; /health/ready checks gateway and internal dependency readiness.
Payload model
Raw request/response content is not stored; technical/billing metadata supports operation and accounting.
Additional route
Primary route and fallback can remain client-controlled.