The sale ended today.
Google stopped selling new Gemini Code Assist Standard and Enterprise subscriptions on October 9, 2026. Existing subscriptions remain supported through their contractual term. Google says customers can add licenses until January 31, 2027.[1]
The renewal clock depends on the plan. Annual subscriptions can auto-renew until January 31, 2027. Monthly subscriptions can auto-renew until December 31, 2027. Those dates are purchase limits, not guaranteed service dates for every account. The contract end date still controls each team's runway.
A working extension can hide a dying purchase route.
The named replacement changes more than the badge.
Google directs customers toward Antigravity through Gemini Enterprise. The current developer-tools overview lists Antigravity 2.0, Antigravity CLI, IDE extensions, and Android Studio support. It also requires a supported Gemini Enterprise edition and an invoiced Cloud Billing account.[2]
That is a procurement and identity change before it is a model change. Record the billing account, edition, region, user role, IDE path, CLI path, and unattended-job path. A successful interactive login does not prove that a build runner or scheduled task has the same entitlement.
Carry policy through the switch.
The replacement docs name roles, overage controls, regional limits, and compliance gaps. They also warn that the first-time policy for files outside working folders can default to Deny. Teams that expect an Always ask prompt must set it explicitly.[2]
Compare old and new settings side by side. Include file reach, network reach, model access, data location, logging, overages, and administrator roles. Do not copy the old policy names and assume the new system enforces the same behavior.
Replay work before moving seats.
Run a matched set of repository tasks through the current route and the candidate route. Include one code edit, one review, one terminal task, one denied file-access probe, and one quota or network failure. Save requested tool, served tool, revision, output, cost, policy result, and reviewer decision.
The sunset notice proves the dates. The product overview proves the documented route and prerequisites. Neither proves that Antigravity fits your repositories, security rules, or acceptance bar. Keep the current route until the new route passes that local test and the rollback path has been exercised.