◆ AI AT WORK · Enterprise
Google capped console purchases of Gemini Enterprise Standard and Plus at 25 seats. Past that, you talk to sales.
Growing a Gemini Enterprise Standard or Plus subscription past 25 seats now runs through a sales representative rather than the console. The invoiced-billing gate also sits in front of Google's AI coding tools.
Chandni Melwani
Founder & Editor
Aug 25, 2026 · 2 MIN READ
The News
Gemini Enterprise is Google's paid AI assistant for companies, sold by the seat. On August 19, 2026, a release note filed under "Change" capped how many of those seats a buyer can purchase without a sales conversation: "If you purchase or modify a seat-based subscription directly through the Google Cloud console, the number of seats is capped according to your Cloud Billing account type: Self-serve (online) and resold accounts: Up to 25 seats per account. Invoiced (offline) accounts: Up to 1,000 seats per account." The note applies to the Standard, Plus, Pay-as-you-go and Frontline editions; the separately documented Business edition is not covered by it. Nothing gets switched off for customers already above the cap: the licences page the note links to says an existing subscription that exceeds the threshold will hit a seat limit error when adding licences through the console, and directs those customers to a sales representative or an allowlist exemption. Google gives no reason for the change in the note itself.
Know More
- — The cap, dated August 19, 2026 and logged as a "Change" rather than a feature: up to 25 seats per account for self-serve (online) and resold Cloud Billing accounts; up to 1,000 for invoiced (offline) accounts. It applies to purchasing or modifying a seat-based subscription directly through the Google Cloud console.
- — The scope: the release notes cover the Standard, Plus, Pay-as-you-go and Frontline editions. Business edition is documented separately, and its own Help Center describes adding seats in-product up to 500.
- — The separate August 18 change: AI developer tools reached general availability for Gemini Enterprise Standard, Plus and Pay-as-you-go editions — but only with an invoiced Cloud Billing account. That launch covers Antigravity 2.0, Antigravity CLI and Android Studio.
- — The separate August 20 change: Antigravity for IDEs became available under the same AI developer tools umbrella, for editions "linked to an invoiced Cloud Billing account that receives an active monthly invoice."
- — Already above the cap: existing seats keep working; adding more in the console returns a seat limit error, and Google's licences page routes those buyers to a sales representative or an allowlist exemption. No rationale or transition timeline is given.
On August 19 a line in Google’s release notes capped console purchases of Gemini Enterprise at 25 seats for self-serve and resold accounts. Invoiced accounts get 1,000. Until that line appeared, the assistant Google sells companies by the seat had no published ceiling on how many a card could buy.
The gap between those two numbers is a procurement department. Invoiced billing is not a checkbox: Google extends credit, runs its checks, and issues a monthly invoice, which in most companies means legal, finance and a salesperson. Twenty-five seats is a team. Growing a Standard or Plus deployment past that size is now an organisational purchase rather than a click, which is a different decision made by different people. The release notes cover four editions — Standard, Plus, Pay-as-you-go and Frontline — and say so at the top of the page. Business edition, the $21-a-seat tier Google sells for teams of up to 300, runs on its own documentation, and its Help Center still walks admins through buying seats in-product up to 500.
That matters because of how these tools have actually spread. For three years the standard path into a company ran through someone’s expense claim: a small group bought a licence, the work got visibly better, and the org caught up later. Meta’s WhatsApp agent shipped on the same logic, free first and billed once it was load-bearing. Google has put a number on where that route ends.
The tooling moved the same way in the same week, and the three changes are separate. On August 18, AI developer tools — Antigravity 2.0, the Antigravity CLI and Android Studio — went generally available for editions with an invoiced Cloud Billing account. On August 20, Antigravity for IDEs arrived on the same terms. Willingness to pay does not open that door; the billing arrangement does.
Customers already past the cap are not being moved. The licences page the note links to says an oversized subscription keeps running and only trips a seat limit error when someone tries to add licences in the console, with a sales representative or an allowlist exemption as the way through. Nothing is switched off; the self-service door closes behind you. Google gives no reason for any of it. Read against the enterprise-controls language in the same week’s entries, it looks like Google routing larger deployments toward accounts it can administer and bill directly, though that reading is inference, not disclosure.
Related
Frequently Asked Questions
Does this force companies already over 25 seats to migrate?
No. Nothing is switched off and no migration is described. The licences page the release note links to says that an existing subscription above the threshold — one originally provisioned through a sales-led offline order, for example — may return a seat limit error when someone tries to add licences through the Cloud console, and that the way through is a Google Cloud sales representative or an allowlist exemption. Existing seats keep working; growth is what moves off the console.
What is the practical difference between self-serve and invoiced billing?
Self-serve means a card on the account and a purchase that completes in the console. Invoiced (offline) billing means Google extends credit and bills monthly, which is an application involving a credit check and a sales relationship. On the buyer's side that is the difference between an expense claim and a procurement cycle.
Why does the invoiced-account requirement matter beyond seat counts?
Because the same gate now sits in front of the tooling. AI developer tools went generally available on August 18 for editions with an invoiced Cloud Billing account, and Antigravity for IDEs followed on August 20 on the same condition. A self-serve buyer cannot reach that stack by paying more; the billing arrangement is the qualifying condition.
Sources
- Google Cloud — Gemini Enterprise release notes: seat quantity limits (August 19, 2026), AI developer tools GA (August 18, 2026), Antigravity for IDEs (August 20, 2026)
- Google Cloud — Get subscriptions and assign licenses for Gemini Enterprise: subscription seat quantity limits
- Gemini Enterprise – Business Edition Help — Get more seats
Chandni Melwani
Chandni Melwani is the founder and editor of New in AI, covering AI agents, M&A, and enterprise adoption. She holds a Master's in Management of Artificial Intelligence from Queen's University and brings a practitioner's perspective from her work in Data and AI leadership.
Follow ↗AI at Work Briefing
Get the five-beat briefing before the market opens.
One email. Frontier labs, AI at work, e-commerce, and the capital crossing borders — decoded daily.
No spam. Unsubscribe anytime.
More from AI at Work
Jobs
California sends a two-part workplace AI ban to Newsom
AB 1883 cleared the legislature on August 30 and goes to Newsom unsigned. Two specific categories of workplace AI tool are prohibited; which one a product falls under determines how much of the emotion-AI market the bill would reach.
Chandni Melwani · US · Aug 30, 2026
Tools
OpenAI proposes cutting off Cursor's model access on November 12
OpenAI says it will wind down the contract that supplies its models to the AI code editor Cursor, proposing a shutoff on November 12, 2026, after SpaceX bought Cursor's maker. Teams standardised on Cursor now have a dated deadline.
Chandni Melwani · US · Aug 28, 2026
Tools
Slack moved AI coding work out of the IDE and into a channel your colleagues can read
Slack launched Slack Code on August 20, giving coding agents their own channels where planning, diffs and approvals happen in front of the whole team.
Chandni Melwani · Aug 24, 2026