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.
30records with vendor text (59%)27records with a matched vendor10matched vendor names
Which suppliers are named most often?
Select a name to inspect its evidence| Vendor | Use cases | Agencies | Lifecycle |
|---|---|---|---|
| Microsoft | 19 | 9 | Microsoft Pre-deployment: 3 (15.8%)Microsoft Pilot: 8 (42.1%)Microsoft Deployed: 8 (42.1%) |
| 3 | 2 | Google Pre-deployment: 2 (66.7%)Google Pilot: 1 (33.3%) | |
| Amazon Web Services | 2 | 2 | Amazon Web Services Pre-deployment: 1 (50.0%)Amazon Web Services Deployed: 1 (50.0%) |
| Anthropic | 2 | 2 | Anthropic Pilot: 2 (100.0%) |
| GitHub | 2 | 2 | GitHub Pre-deployment: 1 (50.0%)GitHub Deployed: 1 (50.0%) |
| OpenAI | 2 | 2 | OpenAI Pre-deployment: 1 (50.0%)OpenAI Pilot: 1 (50.0%) |
| IBM | 1 | 1 | IBM Pre-deployment: 1 (100.0%) |
| Perplexity | 1 | 1 | Perplexity Pilot: 1 (100.0%) |
| Thomson Reuters | 1 | 1 | Thomson Reuters Pilot: 1 (100.0%) |
| xAI | 1 | 1 | xAI Pilot: 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.
Perplexity
1 associated use cases in this filterAgency presence
Reported technologies
Leading mission areas
- Administrative Functions1
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