Netlify Now Lets Teams Cap Each Coder's AI Agent Spend

Netlify shipped two changes to how teams control AI spend within a single day this month. On July 15, Team Owners on Pro plans got the ability to cap how many Agent Runner credits each individual team member can burn per billing period, setting one default limit and overriding it for specific people (Netlify, “Manage AI features”). It followed a day after Netlify split its Pro plan into five credit tiers, from the standard 3,000 credits up to 20,000, instead of one fixed allotment (Netlify blog, “Pro plans now offer more flexibility,” July 14, 2026).

---

What shipped

The per-member controls live in Team Settings under General > AI Enablement. A Team Owner sets one spend ceiling that applies to every member by default, then raises or lowers it for individuals, so a power user can get more room while everyone else stays on a predictable budget. The limit only governs Agent Runners, Netlify’s AI coding-agent feature; it doesn’t touch AI Gateway usage, which is metered separately.

The tier change that preceded it is a pricing structure, not a spend control. Pro still starts at $20 a month for 3,000 credits, but a team can now step up to 5,000, 10,000, 15,000 or 20,000 credits for a flat monthly price instead of buying overage on demand. Tiers of 5,000 credits or higher also roll unused credits into the next billing cycle, while the base 3,000-credit tier doesn’t (Netlify Docs, “Credit-based pricing plans”).

---

Why the order matters

Netlify shipped the bigger credit pool and the way to ration it one day apart, addressing the same complaint from two directions. Its own support forum carries threads from teams whose AI Agent Runner burned through their credits without producing a working site, in one case leaving deploys blocked afterward (Netlify Support Forums, “AI Agent consumed credits but failed to generate website”; “Deploys blocked after AI credits exhausted”). A bigger pool buys more room before that happens. A per-member cap stops one person’s runaway agent from spending the whole team’s pool before anyone notices.

Neither change addresses the complaint underneath both threads: an agent that consumes credits on a run that fails outright. Rationing the spend doesn’t refund it.

Key Takeaways

• Team Owners on Netlify Pro can now set a default Agent Runner credit limit per team member, with overrides for individuals, in Team Settings > AI Enablement (shipped July 15, 2026).
• One day earlier, Netlify expanded Pro from one fixed 3,000-credit allotment to five tiers up to 20,000 credits; tiers of 5,000+ roll unused credits into the next cycle.
• Support forum threads show the underlying problem: Agent Runner credits get consumed even when a run fails to produce a working result, and per-member caps only limit how much one person can lose that way, not whether it happens.

---

What to do

If a team has run into an Agent Runner burning through its shared credits, set a per-member default now and give trusted heavy users a documented override rather than leaving everyone on one uncapped pool. Pair it with a credit tier that gives enough headroom for normal usage before reaching for on-demand overage. Neither change stops a failed agent run from costing credits, so the spend caps are damage control, not a fix for that specific complaint.