Supplier evidence · agency-reported associations
Vendors
Suppliers named in the inventory. These associations establish neither contracts nor spending, market share or a specific model used.
38records with vendor text (100%)38records with a matched vendor10matched vendor names
Which suppliers are named most often?
Select a name to inspect its evidence| Vendor | Use cases | Agencies | Lifecycle |
|---|---|---|---|
| OpenAI | 38 | 12 | OpenAI Pre-deployment: 4 (10.5%)OpenAI Pilot: 14 (36.8%)OpenAI Deployed: 19 (50.0%)OpenAI Retired: 1 (2.6%) |
| Microsoft | 21 | 8 | Microsoft Pilot: 7 (33.3%)Microsoft Deployed: 14 (66.7%) |
| Amazon Web Services | 4 | 1 | Amazon Web Services Deployed: 4 (100.0%) |
| 4 | 3 | Google Pre-deployment: 1 (25.0%)Google Pilot: 2 (50.0%)Google Deployed: 1 (25.0%) | |
| Anthropic | 3 | 2 | Anthropic Pilot: 2 (66.7%)Anthropic Deployed: 1 (33.3%) |
| Perplexity | 3 | 2 | Perplexity Pilot: 3 (100.0%) |
| xAI | 2 | 1 | xAI Pilot: 2 (100.0%) |
| LexisNexis | 1 | 1 | LexisNexis Pilot: 1 (100.0%) |
| Meta | 1 | 1 | Meta Deployed: 1 (100.0%) |
| Palantir | 1 | 1 | Palantir Deployed: 1 (100.0%) |
One use case may name several suppliers. Counts overlap and are not market shares. Unmatched vendor text is preserved in source records.
Agency presence
Reported technologies
Leading mission areas
- Administrative Functions3
- Energy and the Environment1
Names come from the existing vendor matcher. Technology associations use the agency's reported classification; they do not identify the vendor's product or model. Methodology