Government engagements
Classified and CUI-authorized deployments.
TraceOps Commercial is for public solicitations and non-controlled contractor workflows only. Classified, CUI-authorized, or other restricted-data work requires a separate engagement model with the product team. Start with Commercial, then talk to us.
What TraceOps Commercial does today
TraceOps Commercial is the publicly available product. It is designed for public solicitations and non-controlled contractor workflows only and is not authorized for restricted government information.
- Hosted in commercial Microsoft Azure
- AI processing through commercial third-party model providers (see /subprocessors)
- Not authorized for CUI, classified, ITAR-controlled, export-controlled, source-selection sensitive, or other restricted government information
Why classified or CUI work requires a different engagement
The Commercial backend cannot host classified or CUI-authorized work as designed. Programs that need to process controlled data require a separate platform engagement with a re-architected backend, controlled model-access path, and program-specific authorization posture.
- Re-architected hosting on an approved cloud (for example, Azure Government with isolated tenancy)
- Controlled model-access path so commercial third-party AI providers are not in the controlled-data path
- Authority-to-operate documentation and agency-specific data-handling controls
- Dedicated platform instance, separate provisioning, and a separate operational posture
How the engagement works
Engagement is a four-step path from TraceOps Commercial to a controlled-side deployment. Each step is scoped before the next one begins; nothing about controlled data flows through TraceOps Commercial at any point.
- Step 1. Start with TraceOps Commercial on a non-controlled workflow so the team can evaluate the product's review discipline, workflow model, and outputs on representative public data.
- Step 2. Submit a classified-engagement inquiry through the Contact form. Note the agency context and the controlled data categories involved at a high level. Do not include specifics about the data itself or any restricted material in the form.
- Step 3. Scoping conversation with the product team to map the required hosting model, access controls, data-handling posture, authority-to-operate path, and program timeline against your requirements.
- Step 4. Negotiate a custom platform engagement. This is a separate agreement, separate platform instance, separate pricing, and a separate operational team from TraceOps Commercial.
What we will and will not promise upfront
We are transparent about the difference between the available commercial product and a not-yet-built controlled-side deployment. Authorization, hosting, and clearance requirements are program-specific and customer-funded as part of the engagement.
- We will not represent TraceOps Commercial as authorized for CUI, classified, ITAR, or restricted data
- We will not pre-commit to a specific authorization tier (FedRAMP, IL-4/5/6, ATO) before scoping with the program
- We will not request, store, or process any specifics about controlled data through the inquiry form
- We will share what is available today, what would change for a controlled-side deployment, and a realistic engagement timeline once scoping begins
