Insider: Red Hat is capping devs’ bot budgets
Red Hat, the IBM-owned Linux and open-source software firm, has told its developers to limit spending on AI coding tools to $300 per person each month, according to an insider tip received by The Register. Developers have also been barred from pooling or sharing unused token allowances with colleagues. The move marks a notable shift from the company's enthusiastic public stance on AI-assisted coding earlier in the year, suggesting the costs of widespread AI tool use may have outpaced expectations.
The $300 cap sits at the low end of what other organisations reportedly spend: Gartner research cited by DevOps.com found that roughly a quarter of technology leaders already pay between $200 and $500 per developer monthly for AI coding tokens, with about 6% spending more than $2,000. Some developers on Reddit have reported personal spending of $1,000 to several thousand dollars a month, and analysts at Enso Dynamics predicted late last year that $1,000 per developer monthly would soon become standard. Red Hat and Gartner did not respond to The Register's requests for comment, and no figures were provided on the company's previous AI spending levels.
- Red Hat caps developer AI token spending at $300 per month.
- Sharing unused token allowances between developers is now banned.
- Industry spending on AI coding tools varies widely, often exceeding Red Hat's cap.
New here? Start with this
Red Hat is a US software company owned by IBM. It is best known for Linux and other open-source tools, whose underlying code can be used and adapted by others. Its developers, like those at many technology firms, can use AI coding tools to help write or check software.
Many AI coding services charge according to how much their systems are used, often measured in “tokens”, small units of text processed by the AI. Giving developers a monthly budget can help a company manage those costs, while limits on sharing budgets determine how flexibly teams can use them. The issue matters as companies weigh the possible productivity benefits of AI tools against their expense.
Both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
A $300 monthly limit could help Red Hat contain a fast-growing and uncertain expense while ensuring developers have predictable access to AI tools. Preventing staff from pooling allowances may also make costs easier to track and encourage teams to judge tools by the value they deliver rather than by how many tokens they can consume.
The case against
A fixed $300 cap could constrain developers whose work benefits from heavier AI tool use, even if that use saves time or improves output. With some organisations reportedly spending more and no figures given for Red Hat’s prior costs or the returns it has seen, the limit may reflect a blanket restriction before the company has shown how it balances savings against those benefits.