Government Cloud (FedRAMP, GovRAMP, G-Cloud)

Where this market publishes its structure

• FedRAMP Marketplace data (github.com/18F/fedramp-data data/data.json @4b73d9247f, the marketplace's source) machine-readable, 425 packages / 342 CSPs (Compliant 309, In Process 96, Ready 20); 149 providers linked, 112 authorized
• GovRAMP (formerly StateRAMP) Program Participants (govramp.org/program-participants) machine-readable, 425 rows / 364 organizations, server-rendered table; no website column, linked by contact e-mail domain; 101 linked
• UK G-Cloud 15 suppliers (Digital Marketplace A-Z + supplier pages) machine-readable, 2,771 suppliers; linked by contact e-mail domain; 106 linked (distribution)
• FedRAMP Marketplace UI (marketplace.fedramp.gov) not machine-readable: SvelteKit client shell; read through the 18F data file instead
• DoD Cloud Service Catalog / Impact Level provisional authorizations (cyber.mil/dccs, DISA) not machine-readable: Salesforce LWC client app; DISA catalog requires DoD PKI
• CMMC C3PAO Marketplace (cyberab.org/Catalog) not machine-readable: JS storefront; C3PAOs are assessors, not suppliers (not in market)
• FedRAMP 3PAO assessors (data.json Assessors) machine-readable, 58 assessors; not suppliers, not read

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-15 from the 63 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

gravity 3 · other companies invest to build on it

builds-on 5 · publishes apps on other platforms' stores

coverage 1 · reaches banks, carriers, systems or channels (an aggregator)

covered 1 · reached mainly through aggregators

regulated 4 · named in a regulator's register or partners' contracts

standard 12 · listed by a voluntary standard's own directory

mixed 8 · no single mode dominates

long-tail 2 · reached only through iPaaS bridges

distribution 9 · only sells through cloud marketplaces

undeclared 18 · declares nothing we can read: no number

Top workflows by market votes

Workflows (Arazzo) and their phrasing are generated by API Evangelist, ranked by market votes (integration edges in the graph, weighted by channel).

In-market workflows only: a step on the market provider's side maps to this market's business capabilities (), and the partner is not a generic export/notify app. Other workflows are counted as bridges (including any whose steps do not resolve to a capability yet). Methodology. In-market: 16; bridges: 0.