---
title: "How Should a State Agency Procure AI Agents It Can Own and Self-Host?"
slug: "state-agency-procure-ai-agents-own-and-self-host"
author: "ibl.ai"
date: "2026-11-18 14:00:00"
category: "Premium"
sector: "government"
topics: "state agency AI procurement, AI agents procurement, NASPO ValuePoint cloud and software solutions, TX-RAMP, NIST AI RMF, California GenAI procurement, state government AI, self-hosted AI agents government, AI contract terms, source code ownership, state CIO AI"
summary: "A state agency buying AI agents it can own runs six steps: define the use case, assess risk against NIST AI RMF or the state's own tool, pick a vehicle such as NASPO ValuePoint, clear the state's cloud security program, write ownership and data terms, and keep monitoring."
banner: ""
thumbnail: ""
linkedin: |
  How should a state agency buy AI agents it can actually own?

  It is a process question, and the answer runs through six steps.

  1. Define the use case and the data it touches.
  2. Assess risk. NIST's AI RMF is voluntary; California requires its own GenAI risk assessment and CDT consultation for moderate and high risk.
  3. Pick a vehicle. NASPO ValuePoint's new Cloud and Software Solutions portfolio, led by Utah, was awarded September 16, 2026 and runs to 2036, and it covers on-premise software, not only SaaS.
  4. Clear the state's cloud security program. In Texas, TX-RAMP has applied to cloud contracts entered or renewed since January 1, 2022, and configured off-the-shelf platforms are not exempt.
  5. Write ownership into the contract: source code, data return, model switching, logs the agency holds.
  6. Monitor after go-live.

  Step 5 is where most contracts are thinnest, and it is the step that decides whether the agency owns its agents or rents them.

  #iblai #GovTech #StateGovernment #AIAgents #Procurement
---

## The Short Answer

**A state agency procures AI agents it can own by treating ownership as a contract term, not a feature: assess risk, buy through an approved vehicle, clear the state's cloud security program, then require source code, data return and model switching in writing. On ibl.ai you own all the code and the data, and the agency self-hosts it.**

The six steps below follow published state and national guidance: [NIST's AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework), California's [GenAI procurement process](https://www.genai.ca.gov/choose-your-journey/incidental/follow-procurement-process/procurement-process), [NASPO ValuePoint](https://www.naspovaluepoint.org/portfolio/cloud-and-software-solutions) and Texas DIR's [TX-RAMP](https://dir.texas.gov/txramp) program.

The rules differ by state, so treat this as the shape of the process and confirm each step with your state's procurement office.

## What are the steps for a state agency to procure AI agents?

A state agency procuring AI agents typically works through six steps, and California's published process alone has five stages from training to ongoing monitoring.

<table>
<thead><tr><th>Step</th><th>What the agency does</th><th>Published example</th></tr></thead>
<tbody>
<tr><td>1. Define the use case</td><td>Name the workflow, the systems the agent reads, and the data classification</td><td>California starts with GenAI training before the procurement package</td></tr>
<tr><td>2. Assess risk</td><td>Rate the use against a risk framework</td><td>NIST AI RMF 1.0; California's SIMM 5305-F risk assessment</td></tr>
<tr><td>3. Pick a vehicle</td><td>Use a cooperative or state contract, or run a solicitation</td><td>NASPO ValuePoint Cloud and Software Solutions, 2026 to 2036</td></tr>
<tr><td>4. Clear security authorization</td><td>Meet the state's cloud security program</td><td>Texas TX-RAMP Level 1 or Level 2</td></tr>
<tr><td>5. Write ownership and data terms</td><td>Source code, data return, model switching, logs</td><td>California requires GenAI disclosure and reporting language</td></tr>
<tr><td>6. Monitor after go-live</td><td>Assign a contract manager and review the agent's behavior</td><td>California requires a contract manager for every GenAI contract</td></tr>
</tbody>
</table>

The order matters. Ownership terms written after a vehicle is chosen are limited to what that vehicle's master agreement allows, so step 5 has to inform steps 3 and 4.

## How should a state agency assess AI agent risk before buying?

A state agency should assess AI agent risk against a recognized framework before writing the solicitation. The common baseline is NIST's AI Risk Management Framework 1.0, released January 26, 2023, which NIST says "is intended for voluntary use."

NIST added a Generative AI Profile, NIST AI 600-1, on July 26, 2024, and says AI RMF 1.0 is being revised under the White House AI Action Plan.

The framework's four functions, Govern, Map, Measure and Manage, give an agency a vocabulary for the risk file even where state law does not require it.

Some states require their own tool. California entities assess GenAI risk with SIMM 5305-F, and consultation with the California Department of Technology is required for moderate- and high-risk procurements and optional for low-risk ones.

For AI agents the risk turns on actions, not just answers. An agent that reads case files or writes to a system of record needs its permissions, its data paths and its logs in the risk file, alongside the model.

## Which contract vehicles can a state agency use to buy AI agents?

A state agency can buy AI agents through a cooperative contract, an existing statewide contract, or its own solicitation.

One option is newly awarded: NASPO ValuePoint's Cloud and Software Solutions portfolio, led by Utah, was awarded September 16, 2026 and expires September 15, 2036.

The portfolio features 58 awarded suppliers and covers SaaS, IaaS, PaaS, on-premise software and value-added services. That last pair matters for an agency that wants to self-host: the vehicle is not limited to vendor-hosted SaaS.

A cooperative contract only works where the state has signed a participating addendum. NASPO says each addendum "outlines which entities within the state" can purchase; without one, the agency goes to the state's chief procurement official.

Federal vehicles are a separate track. For GSA MAS, OASIS+ and similar routes, see our [guide to government AI contract vehicles](/resources/guides/government-ai-contract-vehicles-mas-oasis-stars).

## What security authorization does a state agency's AI agent need?

A state agency's AI agent needs whatever cloud security authorization the state requires, and Texas shows how binding that can be.

Under Government Code Section 2054.0593, Texas state agencies may only enter or renew contracts for cloud computing services that comply with TX-RAMP, beginning January 1, 2022.

TX-RAMP has two levels: Level 1 for low impact information resources and Level 2 for moderate or high impact ones, per version 3.0 of DIR's program manual. Each cloud service needs its own certification.

One detail corrects a common assumption.

The manual exempts bespoke applications an agency commissions, but says the exemption "does not include commercial off-the-shelf software platforms that are simply configured specifically for agency purposes." A configured AI platform is not exempt by default.

Self-hosting changes where the boundary sits rather than removing it. If the agency runs the software in an environment it already operates, the scoping question is about that environment; confirm the determination with DIR or your state's equivalent and document it.

## What ownership and data terms should a state AI agent contract include?

A state AI agent contract should put ownership in writing, because the vehicle and the security review do not supply it. California already requires GenAI disclosure language in every written solicitation and GenAI reporting language in every written contract.

Beyond disclosure, five terms decide whether the agency owns its agents or rents them.

<table>
<thead><tr><th>Contract term</th><th>What it should say</th></tr></thead>
<tbody>
<tr><td>Source code</td><td>The agency receives the platform's source code under a perpetual license</td></tr>
<tr><td>Data return</td><td>All data, prompts, transcripts and configurations exportable in open formats at no extra charge</td></tr>
<tr><td>Model switching</td><td>The agency can change LLM provider without a contract amendment</td></tr>
<tr><td>Logs</td><td>Audit logs and transcripts are held in the agency's environment</td></tr>
<tr><td>Pricing</td><td>Usage-based against a cap the agency sets, not per seat</td></tr>
</tbody>
</table>

The federal government has moved in the same direction: OMB's M-25-22 asks AI contracts for data portability and protection against lock-in. We covered that memo and a GAO finding on exit costs in [government AI procurement moving to architecture ownership](/blog/government-ai-procurement-architecture-ownership).

## What should a state agency monitor after its AI agents go live?

A state agency should monitor its AI agents continuously after go-live, because an agent's behavior changes when its model, prompts or connected systems change.

California requires every GenAI contract to have a contract manager who continuously oversees and evaluates the technology for risk.

California also covers new capabilities on an existing contract: GenAI added through a contract amendment still requires a risk assessment. Each state entity must report all GenAI purchases into FI$Cal.

Monitoring works only on what the agency can see. On ibl.ai that means [transcripts](/docs/os/analytics/transcripts) of every agent conversation, an [audit log](/docs/os/analytics/audit) of configuration changes, [roles and RBAC](/docs/os/organization-settings/roles) scoping each agent, and [cost analytics](/docs/os/analytics/costs) per agent.

## Where does ibl.ai fit in a state agency's AI agent procurement?

ibl.ai fits step 5 as the owned-stack option: the agency receives the code and runs the platform in its own environment.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, with no per-seat pricing, and deploy anywhere from a state data center to a fully air-gapped network.

ibl.ai is SOC 2 Type II certified. It does not replace the state's own steps: the agency still runs its risk assessment, uses its vehicle, and completes its state's security determination.

ibl.ai is family-owned and operated from New York, NY, and its engineers build alongside an agency's own team, so the agents the state commissions stay the state's.

*Sources: [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) (AI RMF 1.0, January 26, 2023; NIST AI 600-1, July 26, 2024); [California GenAI procurement process](https://www.genai.ca.gov/choose-your-journey/incidental/follow-procurement-process/procurement-process) (California Department of Technology); [NASPO ValuePoint Cloud and Software Solutions](https://www.naspovaluepoint.org/portfolio/cloud-and-software-solutions); [Texas DIR TX-RAMP](https://dir.texas.gov/txramp) and its [Program Manual v3.0](https://dir.texas.gov/sites/default/files/2023-10/TX-RAMP%20Program%20Manual%203.0%20-%20Effective%2012.31.23.pdf). DIR has since published a v3.1 manual; check the current version before relying on section numbers.*

## Why does owning the AI stack matter?

**ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.**

- **You own all the code and the data.** Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.
- **Model-agnostic.** Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.
- **No per-seat pricing.** Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.
- **Deploy anywhere.** Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

[Explore sovereigngovernment.ai](https://sovereigngovernment.ai/)
