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.
24records with vendor text (100%)19records with a matched vendor9matched vendor names
Which suppliers are named most often?
Select a name to inspect its evidence| Vendor | Use cases | Agencies | Lifecycle |
|---|---|---|---|
| Microsoft | 4 | 1 | Microsoft Pre-deployment: 4 (100.0%) |
| 3 | 1 | Google Pre-deployment: 3 (100.0%) | |
| OpenAI | 3 | 1 | OpenAI Pre-deployment: 2 (66.7%)OpenAI Retired: 1 (33.3%) |
| Amazon Web Services | 2 | 1 | Amazon Web Services Pre-deployment: 2 (100.0%) |
| Perplexity | 2 | 1 | Perplexity Pre-deployment: 1 (50.0%)Perplexity Pilot: 1 (50.0%) |
| Salesforce | 2 | 1 | Salesforce Pre-deployment: 2 (100.0%) |
| ServiceNow | 2 | 1 | ServiceNow Pre-deployment: 2 (100.0%) |
| Ask Sage | 1 | 1 | Ask Sage Retired: 1 (100.0%) |
| GitHub | 1 | 1 | GitHub Pre-deployment: 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.
ServiceNow
2 associated use cases in this filterAgency presence
Reported technologies
Leading mission areas
- Service Delivery2
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