aivinay/ai-spend-cap-tracker — explained in plain English
Analysis updated 2026-05-18
Research which companies have capped or cut AI-coding tool budgets and why.
Cite sourced examples when building a case for or against AI spend limits at your own company.
Track industry trends in AI coding tool adoption and cost management over time.
| aivinay/ai-spend-cap-tracker | 0verflowme/alarm-clock | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | — | CSS | Python |
| Last pushed | — | 2022-10-03 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | easy | easy | moderate |
| Complexity | 1/5 | 2/5 | 4/5 |
| Audience | pm founder | vibe coder | developer |
Figures from each repo's GitHub metadata at analysis time.
This repository is not a piece of software but a public, sourced record tracking companies that are limiting or cutting how much their employees spend on AI coding tools. It documents a shift happening in 2026 where organizations that previously encouraged unlimited AI usage are now capping it, a trend the author calls moving from tokenmaxxing to tokenminimizing. The heart of the project is a table listing specific companies, what action each one took, the size of the cap or cut where known, when it happened, which AI tools were affected, and a link to a named news source for every entry. Companies covered include large firms placing dollar caps on tools like Claude Code and Cursor, others cancelling licenses outright in favor of cheaper alternatives, and some centralizing spend through internal tracking dashboards. The project also keeps a section for counter examples, noting at least one company that reversed an earlier restriction and expanded AI tool access instead. The author is explicit about the inclusion rule: an entry only goes into the table if it is backed by a named, linkable source such as a reputable news outlet or an official company statement. Unconfirmed reports are kept separate and marked for verification rather than being added directly. The README also explains the reasoning behind the project, arguing that blanket spending caps are a blunt approach that can hold back the engineers most likely to benefit from AI tools while ignoring other risks like proprietary code exposure, and it points to a related open source project as an alternative approach to routing AI usage more selectively. The data itself is licensed under CC BY 4.0, meaning it can be reused as long as the source is credited, and the project welcomes outside contributions of new sourced entries.
A public, sourced tracker documenting companies that are capping or cutting employee spending on AI coding tools in 2026.
CC BY 4.0: you can reuse and share the data freely as long as you give credit.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
Verify against the repo before relying on details.