Federal IT Dashboard

The United States government's ledger of its own technology spending, run by the General Services Administration on behalf of the Office of Management and Budget to satisfy FITARA reporting obligations. The portal's headline figure reads $102,310.02M of FY2025 IT spending across 26 federal entities - every Cabinet department plus EPA, GSA, NASA, NARA, NSF, NRC, OPM, SBA, SSA, USAID and the U.S. Army Corps of Engineers.

Underneath the charts sit thirteen named data feeds across two domains. The IT Portfolio domain covers the investment roster itself, IT cost pools, IT towers, funding sources, budget account summaries, CIO evaluation history, a contracts report, projects, operational analysis, performance metrics and performance metric actual results; the Web Metrics domain adds security-design/analytics and accessibility measurements. A single government-wide pull of the core IT Portfolio feed returns 7,605 investment records of 31 columns each, spanning fiscal years 2020 through 2025.

That combination - dollars, owners, identifiers and vendor contracts in one keyed corpus - is what makes this more than a transparency site. It is a joinable map of who buys what in American government IT.

Each record is one federal IT investment, flat and comparable across all 26 entities. Two rows straight from the roster:

agency_name    : Department of Commerce
bureau_name    : Bureau of Industry and Security
current_uii    : 006-000552000
title          : BIS Commerce USXPORTS Exporter Support System (CUESS)
type           : Major IT Investments
portfolio_part : Part 1. IT Investments for Mission Delivery
fy2025_funding : 4.092  ($millions)
updated        : 2026-03-31 16:19:30

agency_name    : Department of Commerce
current_uii    : 006-000400800
title          : Census - Field Support Systems
contract_piid  : DOCYA132315BU0042
reference_piid : DOCYA132315BU0042
updated        : 2021-09-20 19:58:18

The first row is a major investment at a Commerce bureau with its FY2025 funding line and a fresh update stamp. The second shows the contracts layer doing its job: a Census field-systems investment carrying the contract PIIDs that name the vendor relationship behind it.

Fifteen core fields ride on every investment record, typed and defined below. All fifteen were verified against live row output during research, so the dictionary describes what actually arrives rather than what a brochure promises.

Two design choices make the corpus unusually well behaved. First, current_uii is a genuine primary key: the same identifier appears across the portfolio, contracts, projects and performance feeds, so one join attaches dollars to vendors to evaluations. Second, the six fiscal-year funding columns sit side by side on a single row - a FY2020-to-FY2025 trend line with no panel assembly required.

Geography - the entire United States federal establishment: 26 reporting entities from the Cabinet departments to EPA, GSA, NASA, NARA, NSF, NRC, OPM, SBA, SSA, USAID and the Army Corps of Engineers, each broken down to bureau level via paired agency and bureau codes.

Temporal - fiscal years 2020 through 2025 in parallel columns for both internal (agency) funding and contributions (transfers), so six-year trajectories arrive pre-built. Record-level updated_time stamps ran to at least 2026-03-31 in the government-wide pull, and successive Datadory deliveries accumulate into a history the source itself does not present.

Granularity - one row per IT investment per agency/bureau, roughly 7,600 of them government-wide. The contracts feed drops another level, resolving each investment into individual contract PIIDs; the performance feeds resolve it again into metric actual results.

API, files, or your warehouse. Daily, weekly, or hourly.

• GovTech vendor targeting. Agency and bureau codes tell you who owns the money; investment titles and descriptions tell you what they are building; the contracts feed tells you who currently holds the work. Cross-reference the incumbent roster against the Clutch and DesignRush outsourcing directories to size the displacement opportunity.
• Market sizing of federal IT demand. Sum funding columns by entity, bureau, investment type or mission-delivery area to quantify where the $102B actually concentrates - and how each slice moved between FY2020 and FY2025.
• Procurement due diligence. Contract PIIDs linked to investment UIIs give a defensible answer to 'who serves this account', with parent/idled relationships preserved through reference PIIDs.
• Transparency research and journalism. CIO evaluation history, operational analysis and cost-savings views put grades and savings claims next to dollar lines, which is exactly the pairing accountability stories need.
• Portfolio benchmarking. Shared-services categories, portfolio parts and investment types let consultancies position any single agency against the government-wide baseline on identical fields.

Competitive intelligence and product teams get a keyed map of every federal IT program, its owner and its incumbent; see competitive intel product teams use cases. Sales and growth teams turn bureau codes and contract PIIDs directly into account plans. Journalists and academics get statutorily-mandated numbers with enough structure to cite; see journalists academics use cases. Investors and quants track federal demand signals across six fiscal years; see investors quants use cases. Developers and builders get a stable UII-keyed corpus to build enrichment pipelines against; see developers builders use cases.

Because the useful test is a join, not a glance. A sample comes back cut to the agencies, investment types or fiscal years you care about, with current_uii intact so you can verify immediately that portfolio rows resolve against contracts and evaluation history. Test whether your account list, CRM territory or research panel keys cleanly onto the federal hierarchy before anything reaches production. Start small: get a sample of this dataset scoped to the slice you will actually use, or browse the data processing outsourced services data hub for companions.