About GOVSPENDING.ORG

GOVSPENDING.ORG aggregates, normalizes, and presents U.S. federal economic and fiscal data. We pull from the U.S. Department of the Treasury (fiscaldata.treasury.gov), the Federal Reserve Economic Data (FRED) service, the Bureau of Labor Statistics, and Congress.gov. We do not generate estimates, run forecasts, or overlay any proprietary model on the underlying data. When we present a number, it comes from a federal agency's published dataset.

Our role is to make that data more accessible: unified presentation across agencies, consistent date formatting, search and discovery across ~100 series, chart visualizations, and free CSV / JSON exports. Federal fiscal data belongs in the public record, and we believe it should be navigable in the browser without logins, paywalls, or API keys.

Primary sources only. Every indicator links back to its official federal agency. No secondary aggregators, no third-party models, no modeled data without clear labeling.

No editorial opinion. Our copy describes what the data measures, how it's calculated, and what it has done historically. Dashboards do not take policy positions, make recommendations, or advocate for specific fiscal or monetary outcomes.

Transparent corrections. If we find or are told about an error — a broken label, a miscited source, a calculation bug — we fix it in the source code and the fix ships in the next build. Every meaningful change is recorded in the project's public git history.

No paid placement. We do not accept sponsored content, sponsored series, or affiliate revenue. Inbound links to federal agencies are editorial.

GOVSPENDING.ORG is an independent project. It is not affiliated with any federal agency, political party, think tank, media organization, or advocacy group. It is not funded by advertising, subscriptions, donations, grants, or sponsorships. Server and hosting costs are borne by the project maintainers directly.

If that changes — if the project takes external funding, adds a commercial tier, or accepts sponsorship — we will disclose the relationship here before the change ships.

If you find a data discrepancy, spot a bug, or want to suggest a new indicator or dashboard, please open an issue on the project repository. That's the canonical place to reach the editorial team and guarantees a public record of the question and the response.