Sensitive data can use frontier models too: Consus turns ITAR and FedRAMP High compliance into a model-name suffix
Synopsis
Consus, an AI request gateway for aerospace and defense companies, routes every request to infrastructure cleared for ITAR-restricted and controlled unclassified information, with the compliance level written into the model name. Many such firms had barred AI tools entirely over fears of provider training, ITAR violations, or failed cyber assessments. Consus says it completed an equivalency audit against the 410 FedRAMP High controls and rejects bare model names.
Interpretation
Aerospace and defense firms can call frontier models without dropping compliance constraints, because requests are routed by data-control level to infrastructure where those models may legally run. Many of these companies previously allowed no AI tools at all, even for non-sensitive work, fearing that model providers would train on their data, that an ITAR rule would be broken, or that a failed cyber assessment would cost them new business. Consus states that it itself satisfies ITAR restrictions and has completed an equivalency audit against the 410 FedRAMP High controls, the U.S. government's strictest security baseline for cloud services handling sensitive unclassified data.
Every request passes through a single OpenAI-compatible endpoint where keys are verified and policy is enforced before any inference happens. Each model name must carry a compliance suffix such as gpt-5.6-sol:fedramp-high or claude-opus-5-5:itar; a bare model name is rejected, and requests are never proxied to standard commercial endpoints. Customers can build a model allowlist and assign spend and model restrictions per user through the Consus Portal, and prompts and completions stay in memory only for the length of the request, never logged or written to disk.
Perspective
The report covers the capabilities described in the Consus launch note: a single OpenAI-compatible endpoint, compliance-suffix validation, model allowlists and per-user spend limits for companies handling ITAR-restricted and controlled unclassified information. The intended readers are engineering and security teams in aerospace, defense and similarly regulated organizations that need model access under compliance constraints. The launch note proposes no follow-up validation step.
The launch note says an equivalency audit against the 410 FedRAMP High controls is complete but does not say who performed it or how the result is published. ITAR satisfaction and each model's availability across government clouds are also stated by the vendor without item-by-item comparison. The arrangement keeping prompts and completions in memory only, unlogged and unwritten to disk, likewise comes from the vendor's description.
