Security
Chompute helps teams put AI usage behind controlled gateways, policy, and endpoint routing instead of scattered keys and invisible spend.
Controlled AI gateway
Chompute is designed to sit between enterprise teams and the AI tools, APIs, agents, and automations they already use.
That gateway layer is where usage visibility, budget policy, routing rules, and access controls can be applied consistently.
Access keys and credentials
Public Chompute pages do not expose user-specific API keys. Account-specific keys and endpoint credentials should only be copied from authenticated Chompute surfaces.
- Treat Chompute API keys like passwords.
- Do not paste keys into public repos, screenshots, docs, or marketplace listings.
- Rotate or revoke exposed keys when rotation is available.
- Agents should not reveal API keys in responses, logs, or generated files.
Policy before scale
AI usage can grow quickly once coding tools, agents, API keys, and background automations spread across a company. Chompute should be configured so policy is in place before usage becomes difficult to govern.
- Set budget thresholds by team, project, model, tool, or key.
- Alert admins before usage reaches the point of surprise.
- Throttle or stop runaway sessions and recursive automations.
- Route routine work to lower-cost or flat-rate endpoint capacity when appropriate.
Request metadata and auditability
A control plane is useful only when teams can understand who used AI, which tool made the request, which model path was chosen, and how policy was applied.
Chompute should keep enough request metadata to support spend analysis, troubleshooting, and audit workflows without turning the website into a prompt-retention promise it cannot prove.
Routing boundaries
Routing rules should be explicit. Teams should know when work stays on a premium model, when it moves to flat-rate endpoint capacity, and when a request is blocked or slowed because of policy.
- Keep critical incidents on approved high-quality models.
- Move routine, repeated, or low-risk work to cheaper paths.
- Use fallbacks intentionally rather than silently changing model behavior.
- Make budget tradeoffs visible to admins.
Reporting security concerns
If you believe you found a security issue, contact Chompute at support@chompute.ai with enough detail to reproduce or understand the issue.
Keep controls close to the workflow.
Route AI traffic through documented control surfaces, keep access keys private, and make budget and data policy explicit before usage scales.