{"schemaVersion":1,"editionId":"2026-10-29","title":"Gemini 4 Carbon begins with restricted access","dek":"What Google’s announcement means for teams considering its next coding and security model.","coverageNote":"Coverage of Google’s October 28, 2026 Carbon announcement and Fairwind documentation retrieved October 29. Availability and performance statements come from Google; this report does not establish access in an individual account or independently test the model.","summaryIntro":"Eligibility is the first decision point for teams considering Carbon.","publishedAt":"2026-10-29T19:41:54.068Z","updatedAt":"2026-10-29T19:41:54.068Z","version":1,"items":[{"id":"gemini-4-carbon-restricted-access","kind":"news","title":"Gemini 4 Carbon: check access before planning a migration","category":"Models & Agents","eventDate":"2026-10-28","status":["announced","company-claim"],"sourceIds":["S1","S2"],"short":"Google announced Gemini 4 Carbon on October 28 for extended coding and cybersecurity work. Its initial rollout is limited to selected cyber defenders, with broader product access still forthcoming.","claims":[{"text":"Google lists introductory prices of $2 per million input tokens and $10 per million output tokens; later rates are $4 and $20, with no expiry date specified.","sourceIds":["S1"]}],"long":[{"text":"Google plans to start with a subset of cyber defenders this week, then expand to additional trusted partners through Fairwind. The announcement gives no firm date for wider developer, business or consumer access.","sourceIds":["S1"]},{"text":"Fairwind prioritizes governments, critical infrastructure and core technology platforms. Applicants contact their Cloud account team and undergo organizational vetting. Its documentation still describes Argon; membership should not be taken as confirmation that Carbon is enabled.","sourceIds":["S1","S2"]},{"text":"Our interpretation: eligible security teams should confirm Carbon-specific access before designing an evaluation. Other teams should wait for a usable release and documented terms before committing to a migration. Compare costs at both announced price levels rather than budgeting indefinitely at the introductory rate.","sourceIds":["S1","S2"]},{"text":"Google reports stronger coding and security performance, but says its external security benchmark evaluations ran without guardrails. These are vendor-reported results, not our independent tests or proof of deployed performance. Documentation-based; not hands-on tested.","sourceIds":["S1"]}]}],"sources":[{"id":"S1","title":"Gemini 4 Carbon: our next frontier model","publisher":"Google / Koray Kavukcuoglu","url":"https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-carbon/","publishedDate":"2026-10-28","kind":"vendor-announcement"},{"id":"S2","title":"Fairwind Program","publisher":"Google DeepMind","url":"https://deepmind.google/fairwind-program/","publishedDate":null,"kind":"official-product-documentation"}],"review":{"passed":true,"reviewedAt":"2026-10-29T19:41:21.146Z","method":"source-check"},"corrections":[],"canonicalUrl":"https://aidaywire.com/briefings/2026-10-29","language":"en","aiGenerated":true,"summary":"Eligibility is the first decision point for teams considering Carbon.\n\nGoogle announced Gemini 4 Carbon on October 28 for extended coding and cybersecurity work. Its initial rollout is limited to selected cyber defenders, with broader product access still forthcoming.","fullText":"Gemini 4 Carbon: check access before planning a migration\n\nGoogle plans to start with a subset of cyber defenders this week, then expand to additional trusted partners through Fairwind. The announcement gives no firm date for wider developer, business or consumer access.\n\nFairwind prioritizes governments, critical infrastructure and core technology platforms. Applicants contact their Cloud account team and undergo organizational vetting. Its documentation still describes Argon; membership should not be taken as confirmation that Carbon is enabled.\n\nOur interpretation: eligible security teams should confirm Carbon-specific access before designing an evaluation. Other teams should wait for a usable release and documented terms before committing to a migration. Compare costs at both announced price levels rather than budgeting indefinitely at the introductory rate.\n\nGoogle reports stronger coding and security performance, but says its external security benchmark evaluations ran without guardrails. These are vendor-reported results, not our independent tests or proof of deployed performance. Documentation-based; not hands-on tested.","checksum":"41bfb762b81043659257fbfa47ce6b7baf72d556f82bdbd6a999cf61167e366f"}