Questions before a decision.

A software subscription on contract that includes the deployment scope described in the SKU. AI Data Guard is a composition template included with it. The agency orders one line from the Contracts page. The delivery partner performs the deployment.

Start with Observability in the first quarter to produce the AI Use and Exposure Report. Make the Adoption decision in the second quarter with the Observability fee credited in full. Expand by mediation point as further use cases are approved. Carahsoft quotes each step on the agency's vehicle.

Yes. Observability and Adoption are on the Contracts page now. Deployment is scheduled with the delivery partner at order and runs on the partner's timeline, which is confirmed on the quote.

Yes. The Contracts page lists the state and local vehicles. State fiscal years vary; the order can be aligned to the agency's budget cycle.

Yes. AI Data Guard Observability is available as a three-month term. It produces the AI Use and Exposure Report, and the fee credits forward in full against the first year of an Adoption subscription.

The Observability SKUs carry a guarantee: refunded in full if the Programmable Data Agent cannot access the required data within seven days of deployment.

Yes. A three-year Adoption subscription is available with the rate held for the full term.

Email TomorrowX@carahsoft.com or call (571) 590-6500.

An authorized partner within the Carahsoft ecosystem, or one of TomorrowX's global partners authorized to deliver in US public sector with appropriate clearance. Carahsoft names the partner on the quote. TomorrowX does not access or operate within the agency network.

As a container in the agency's own environment, cloud or on-premises.

For Observability, the agent is placed beside an agreed AI traffic source and data access is confirmed within seven days. For Adoption, the fixed scope in the SKU covers deployment, configuration, connection to agreed identity and logging services and handover. The delivery partner agrees the schedule at kickoff.

First-line support is provided by the delivery partner for what it builds. TomorrowX supports the control point under the license terms. There is no SLA on a template.

No. Policy is configured through the platform's Editor and Console. Business and data analysts can work with the delivery partner on policy; the agency's engineers retain governance over protocols, security, deployment and performance.

The platform runs inside the agency's own environment and authorization boundary. It is not SaaS. The agency's authorizing official determines how it is treated within the existing authorization process. TomorrowX supplies the architecture and control documentation the assessment needs.

Prompts and responses stay between the agency and its chosen model provider, governed at the mediation point. Nothing is sent to TomorrowX. TomorrowX does not receive agency data. There is no call-home function: the software never contacts TomorrowX to validate a license and needs no outbound access to run.

It is provider-independent. Commercial model providers and locally hosted models are governed the same way. The agency can change model without changing policy. The number of providers makes no difference to the license. Adding one is a configuration change.

Fail-open or fail-closed is set by configuration and agreed per protected path. Deployment is active/active with recovery by DNS switchover.

Every policy decision is recorded with its operational context according to the configured logging policy, and is available for audit, inspector general review and incident response.

A live view of AI use, data exposure and consumption through the Console for the whole term, and at the end of it the AI Use and Exposure Report: AI endpoints observed, data classes crossing the boundary, consumption by provider and cost center, and the policy gaps found. It is evidence for the agency's AI use-case inventory, produced from the data path rather than a survey.

Renew, extend to additional mediation points or environments on a quoted basis, or stop. Nothing is stranded: the policy, evidence and configuration remain the agency's.

The Partners page sets out why to build a practice around Data Mediation™ and how partners are selected: a demonstration, then the business plan the partner intends to enact.

Yes. It is one architecture. Cyber and interoperability outcomes are proven through a scoped Proof of Capability and Value on a defined system or connection, and licensed by mediation point.