Security and data handling
Lumoswitch separates management from the synchronous inference data path. Downstream clients call the Lumoswitch inference service through a restricted public ingress, and Lumoswitch Runtime calls the final model provider. Understand which credentials the control plane stores, which request data Lumoswitch Runtime and the provider process, and what local client files can contain.
Credential handling
| Credential | Purpose | Handling |
|---|---|---|
| Account password | Console sign-in | Stored as a one-way password hash |
| Lumoswitch access key | Calls to the Lumoswitch Runtime inference ingress | Full value shown once; Lumoswitch stores only the runtime token identity and prefix |
| Provider API key | Lumoswitch Runtime calls to the model provider | Encrypted by Lumoswitch and synchronized to the controlled runtime; never returned in list responses |
Credentials are not interchangeable. Downstream clients should not receive provider keys, and model requests never use an account password.
Request data
The Lumoswitch Control API does not receive or proxy synchronous inference requests and does not store prompts or responses. The Lumoswitch Runtime sends the content required for a request to the selected provider, then exposes usage facts through Spend Logs for asynchronous import by Lumoswitch. Evaluate both the Lumoswitch Runtime deployment and provider data policies before transmitting sensitive information.
- Do not send passwords, verification codes, private keys, or unrelated personal data.
- Minimize business identifiers and user content.
- Separate test and production configurations and keys.
- Select upstreams that meet data-region and compliance requirements.
Usage and source data
Lumoswitch currently imports request identity, model, token, cost, status, and known configuration bindings from Lumoswitch Runtime asynchronously for accounting, dashboards, and usage investigation. The public implementation does not import source IP, country/region, ASN, User-Agent, or client fingerprints from the inference ingress. Documentation and support procedures must not assume those fields exist.
Local client files
Some generated client configurations can contain plaintext access keys. Check whether the file is tracked by Git, prefer environment variables or OS secret storage, and never share configuration through screenshots or public tickets. Disable and rotate a key after device or file exposure.
Network and least privilege
Custom base URLs cause the Lumoswitch control plane to access user-supplied locations during model discovery and connection tests, and cause the Lumoswitch inference service to access them during inference. Production blocks private, loopback, link-local, and metadata addresses by default to reduce SSRF risk. Local upstream access must be explicitly permitted by the instance operator.
Restrict keys to required client-facing model names, use reasonable RPM limits, isolate environments, and grant provider credentials only the permissions they need.
Incident response
- Access-key leak: disable, replace, migrate clients, then delete the old key.
- Provider-key leak: revoke or rotate at the provider, update Lumoswitch, and rerun connection tests.
- Suspicious account access: change the password, revoke all sessions, and review configurations, keys, projects, and upstreams.