If your developers get Gemini Code Assist through Gemini Enterprise, access ends March 31, 2027, and Google's named replacement does not support SOC 2 or ISO 27001. Google's November 6 release note sets the date and points developers to Antigravity. Google's AI developer tools overview, checked November 8 (the page carries no date), lists those certifications among the ones Antigravity lacks. Check your audit scope before you plan the migration.
Standalone Code Assist buyers run on a separate clock, with January 31, 2027 as the date to watch. Which clock you are on decides whether you have a fallback.
What Google Changed on November 6
The November 6 notice puts a fixed end date on a benefit Google had tied to contract terms seven weeks earlier. The Gemini Enterprise release notes say bundled Code Assist entitlements for existing Standard and Plus subscriptions "will end on March 31, 2027," and that support until then is limited to the Gemini 3.x model family. The September 17 entry on the same page said existing subscriptions would keep access until the end of their term. A contract running past March 31 now loses the entitlement partway through, and the note mentions no credit or price change for that.
Google's sunset notice and deprecations table set three dates, depending on how you bought:
| If you have | Date | What happens | Fallback |
|---|---|---|---|
| Code Assist bundled in existing Gemini Enterprise Standard or Plus | March 31, 2027 | Entitlement removed | None documented; new standalone sales ended October 9, 2026 |
| Standalone annual Standard or Enterprise | January 31, 2027 | Last auto-renewal and last day to add licenses | Supported to the end of the contract |
| Standalone monthly Standard or Enterprise | December 31, 2027 | Last auto-renewal (license additions still stop January 31, 2027) | Supported to the end of the contract |
Google's deprecations table lists no shutdown date for any of these rows, a gap TechInformed noted in October. The renewal cutoffs are the last commercial events Google has named.
Bundled customers have the harder position. The deprecations table says that after October 9, 2026, "you can no longer purchase new Gemini Code Assist Standard or Enterprise subscriptions." Put that beside the March 31 date and a team on the bundle has no documented way to stay on Code Assist after March. If you believe your account has an exception, get it in writing.
Standalone customers can buy time. The sunset notice says "Existing Gemini Code Assist subscriptions will remain supported until the end of your contractual agreement," so an annual term that auto-renews in late January 2027 should carry support into January 2028. That is an inference from the notice, so confirm it against your order form. The price of staying is the model freeze: the same notice limits Code Assist to Gemini 3.x, while Google's release notes show Gemini 4 Argon reaching AI developer tools on October 13.
Where Antigravity Falls Short of Code Assist on Compliance
Google documents Antigravity as outside the SOC and ISO programs that it lists for Code Assist. The overview page and the Gemini Enterprise compliance page carry the same sentence: "Antigravity in Gemini Enterprise doesn't support the following compliance certifications and security controls." Compare that list with Code Assist's security page and Google's Gemini certifications table, both checked November 8:
| Control | Gemini Code Assist | Antigravity in Gemini Enterprise |
|---|---|---|
| SOC 1, SOC 2, SOC 3 | Listed | Not supported |
| ISO 27001 | Listed | Not supported |
| ISO 42001 | Listed for Gemini products in Google Cloud | Not supported |
| FedRAMP Moderate and High | Not on the certifications table | Not supported |
| IL4, IL5, ITAR | Not on the certifications table | Not supported |
| Access Transparency | Not supported | Not supported |
| Copyright indemnity | Named a Generative AI Indemnified Service | Not addressed in the enterprise docs |
| Private-repo code customization | Enterprise edition feature | Not addressed in the enterprise docs |
Google's certifications table excludes Code Assist on GitHub, so check that row separately if you use the GitHub integration. Code Assist's security page says its Standard and Enterprise editions received the SOC and ISO 27001 certifications and does not mention the Gemini Enterprise bundle, so a bundled customer should confirm with Google that its seats were covered.
The table narrows the problem. A FedRAMP Moderate or High, IL5 or ITAR program gets no worse answer from Antigravity, because Google's certifications table does not list those programs for Code Assist, its Gemini for Government guidance files Code Assist under unauthorized features, and Access Transparency is unsupported on both. The new exposure is SOC and ISO, the evidence a commercial SaaS company or a bank's vendor-risk team typically asks for. The Gemini Enterprise compliance page says the Agentic AI Service in its Standard and Plus editions and Gemini Notebook Enterprise "have many of the following certifications," then carves Antigravity out. A procurement team that confirms Gemini Enterprise is certified and stops there will miss the carve-out.
One question stays open. The exclusion names "Antigravity in Gemini Enterprise," while the overview page lists the Antigravity app and CLI, Antigravity for IDEs, and Android Studio as separate rows. Google does not say whether the IDE extensions, the direct replacement for Code Assist in VS Code and JetBrains, fall inside it. Assume they do until Google tells you otherwise.
The strongest case for Google is that this is a timing gap in a young product. AI developer tools reached general availability on August 18, and audit reports trail new products. GitHub followed that sequence with Copilot: it added Copilot Business and Enterprise to its ISO 27001 scope in May 2024, published a SOC 2 Type 1 report that June, and said a Type 2 report covering April through September 2024 would follow. Antigravity's enterprise documentation also says sessions run under Google Cloud's "enterprise security controls" and that telemetry and model interactions are logged to your own project. Those controls count for something with a security team. An auditor sampling your SOC 2 controls still needs a report, and none of the Google pages reviewed for this piece gives a date for one.
What Moving to Antigravity Does to Budget and Data Residency
Google has not published the numbers a finance team needs to compare the two tools. The sunset notice contains no transition pricing. The quotas page gives no per-edition quota or overage rate for AI developer tools, and it says their quotas reset every seven days from the first prompt, while the editions page refers to "monthly seat credits" that apply only to first-party Gemini models. Partner models such as Claude bill as pay-as-you-go usage once an administrator enables them.
The security control you would most want adds its own cost. The Antigravity Enterprise Gateway, generally available since October 20, lets you inspect and audit model traffic and enforce egress policy. Gateway requests bill pay-as-you-go and do not draw on seat quotas, and a developer cannot use the gateway and a Google Account sign-in at the same time. If your security team requires the gateway, the seat quota you already bought goes unused for that traffic.
Residency now depends on which model a developer picks. The Gemini Enterprise locations page says AI developer tools follow the at-rest residency and machine learning processing commitments of the selected model. Gemini 4 Argon, 3.7 Flash and 3.6 Flash support both in the US and EU, Gemini 3.1 Pro supports them in the US only, and Canada, India, Japan, Singapore and the UK support neither for these tools. A model that is unsupported in your app's location routes to global, which has no regional residency. Google's certifications page marks data residency at rest as supported for Code Assist but names no regions, so a UK or Japan team should confirm what it has today before treating this as a change.
Two smaller checks belong on the list. The standalone Antigravity IDE "is not supported for enterprise deployments," per the enterprise docs, so developers who installed it on their own are outside the managed path. And Google's docs said on August 21 that admin URL allowlists were not yet honored. That line was gone from the enterprise docs on November 8, so confirm the current behavior before you count the console as an egress control.
Who Should Renew, Move or Leave
Renew standalone Code Assist if you need SOC or ISO evidence this audit cycle, and move to Antigravity only for work outside that scope. That recommendation holds until Google publishes an audit date or an in-scope list that names Antigravity.
If you are standalone and in scope, let the annual subscription renew if its renewal date falls by January 31 and buy the seats you expect to need, because additions stop the same day. You accept Gemini 3.x for the term.
If you are on the bundle and in scope, you have until March 31 and no documented Code Assist path, so start evaluating a certified alternative now. Cursor says it holds a SOC 2 Type II attestation plus ISO 27001:2022 and ISO 42001:2023 (page updated August 25, 2026). Anthropic lists SOC 2 Type I and II, ISO 27001 and ISO 42001 for its commercial products, and the Claude Code docs point to its Trust Center for the reports, but neither page says Claude Code is in scope for each one. For GitHub Copilot, the public scope statement cited above dates from 2024, so ask GitHub for its current report. These are vendor statements, and none of them lists FedRAMP, so pull each report and read the system description. The 500-seat buyer's guide and the security-review comparison cover the data-path questions.
If your repositories sit outside any audit or customer commitment, move to Antigravity and take the newer models. One caution for teams that mostly use completion: Manoj Chandra Jha of Nord-IQ Research told InfoWorld in August that buying the license mainly for governance is unlikely to pay off for basic autocomplete-style use, and InfoWorld reported his view that the extra cost is justified only for teams running autonomous, multi-turn agents.
What to Do Before January 31 and March 31
This Week:
- Have whoever owns the Google Cloud contract list every Code Assist seat by source (bundled, standalone annual, standalone monthly), with its renewal date and term end, on one sheet.
- Ask your compliance lead whether Code Assist appears in your SOC 2 system description, your ISO statement of applicability or any customer security addendum. If it does, a replacement needs the same evidence.
- Send your Google account team five questions and ask for written answers: when Antigravity enters SOC and ISO audit scope, whether the IDE extensions fall under the exclusion, whether Antigravity is a Generative AI Indemnified Service, whether code customization settings carry over (Google's sunset notice is silent, as TechInformed reported), and what happens to bundled seats on April 1.
Before January 31, 2027:
- Decide on each standalone annual subscription, and place any license additions you will need for the final term.
- Run an Antigravity pilot on repositories outside your audit scope, with one model list and one location set by an administrator, and record seven-day quota consumption per developer.
- If you are on the bundle and in scope, shortlist one alternative and start its security review.
Before March 31, 2027:
- Move bundled users to the tool you chose, and assign the Gemini Enterprise User role for Antigravity access: the overview page says the Admin role does not grant it.
- Migrate command-line users with the Antigravity CLI migration guide linked from Google's sunset notice, then remove Gemini CLI from your approved list once the move is done.
- Update your vendor inventory and your audit evidence in the same change, so the control record matches what developers are running.
The Bottom Line
Google has retired Code Assist in stages for five months. Consumer tiers stopped serving requests on June 18, console purchases were restricted on September 4, online Gemini Enterprise renewals lost the feature on September 17, sales ended October 9, and the bundle received its end date on November 6. A team that read only one of those notices would have the wrong plan. Antigravity may well earn its certifications, and a customer that needs ISO 42001 evidence would then have a Google option again, but your January renewal comes first.
Put the SOC 2 question to your Google account team this week and get the answer in writing before January 31.