Omni 1.1 lives in Flow and AI Studio

Omni 1.1 Flash lives in Google’s doors: Google AI Studio, the Gemini Enterprise Agent Platform, Google Flow for AI Plus / Pro / Ultra, and scene extension in the Gemini app. That map is Google’s 27 August 2026 Keyword post. Versely still publishes Gemini Omni Flash Edit and Gemini Omni Video. There is no /models/gemini-omni-1-1-flash. 1.1 is not a Versely slug. Flow is still a Veo-and-Omni surface, not a studio. Keep the rows we bill. Use Google’s 1.1 doors when you need a 1.1 control. Come back to caption.

This page is the access map. It is not a changelog of 10s memory, 360p drafts, or first-last — those are other posts. It is also not Google Flow is a Veo surface, not a studio. That page is Flow versus Veo. This page is where 1.1 actually runs.

The four Google doors, named

Google AI Studio. Google’s developer console. The Keyword post says start building with Omni 1.1 there, model id gemini-omni-1.1-flash. This is the door if you are wiring 1.1 into a tool, a draft room, or an internal app. It is not where a social editor should live all week. It is where a developer tries scene extend, first-last, 360p, and 3s video ref against Google’s API.

Gemini Enterprise Agent Platform. Google’s enterprise API path. Same model, different procurement. If your company already buys Gemini through that platform, 1.1 is a line item there. It is still Google’s meter, Google’s identity stack, Google’s output watermarking. It is not a Versely credit.

Google Flow, for AI Plus / Pro / Ultra. Flow is Google’s editor-shaped launcher. It was introduced as a filmmaking surface for Veo, Imagen, and Gemini. As of 27 August 2026, Omni 1.1 is available to those Gemini paid tiers in Flow. That does not make Flow a studio. It makes Flow a second Google model on the same furniture. You still cannot pick Seedance, Kling motion control, or a 30-second Seedance 2.5 pass inside Flow. You still caption somewhere else.

Gemini app, scene extension. Google says scene extension is available to Plus / Pro / Ultra in the Gemini app. That is the consumer chat door for the 10s-context, 10s-increment, 40s-cap extend. It is a convenient place to continue a clip. It is a bad place to run a brand kit, a caption style, or a failover when Omni is the wrong family.

Google also names customers already on Omni Flash via the Agent Platform: Adobe Firefly, Figma Weave, Runway, GMI Cloud. That is Google’s customer list, 27 August 2026. It is proof Omni Flash is in other people’s products. It is not a reason to assume Versely silently renamed a row to 1.1.

What Versely actually bills

Two published Omni rows. Read them like SKUs.

Gemini Omni Flash Edit: video-to-video, conversational edit, from 50 credits, audio off on the card. You already have a clip. You change a thing. Blocking stays. This is the June Omni skill, still the right retouch when the take is 90% right.

Gemini Omni Video: text-to-video, image-to-video, reference-to-video; 4s / 6s / 8s / 10s; 720p / 1080p / 4K; from 29 credits; quota images + videos*2 + character_ids <= 7. This is how you start an Omni-family clip on this catalog.

Neither row is 1.1’s forty-second extend, 360p draft tier, or first-last interpolator as Google described them on 27 August. If a teammate pastes the Keyword URL into a ticket titled “turn on Omni 1.1,” the answer is: we have Omni Flash Edit and Omni Video; 1.1’s new controls are on Google’s doors until a catalog row says otherwise. Do not invent the slug to close the ticket.

Next to those two sit the rest of Google on this catalog: Veo 3.1 (4 / 6 / 8s, 4K, from 64 credits, native audio), VEO 3.1 Reference to Video (8s, from 128 credits, up to three stills), VEO First Last Frame (4 / 6 / 8s, 4K, from 64 credits), VEO 3.1 Extend Video. Flow will show you Veo and Omni. The catalog shows you which Veo job. Pick the job.

The AI video generator is the Versely launcher. It is the honest equivalent of “press generate.” The rest of the app is why you do not live in Flow: captions, other families, one credit pool.

Flow plus 1.1 is still a surface

Adding Omni 1.1 to Flow does not answer the studio test. The test from the Flow piece still holds. List the last ten clips you shipped. If eight were Google-shaped scene clips and two were accidents, Flow is a tolerable house — you will still caption somewhere else. If four needed a different family (30-second hold, motion control, silent cheap T2V, a stills lock on Flux), Flow is the reason those four were forced through Google or bounced through a second paid app.

1.1 makes Flow better at Google’s longer Omni stories: ten seconds of memory, forty-second cap, 360p drafts, first-last, 3s video ref. That is a stronger surface. A stronger surface is not a roster you can leave. Seedance 2.5’s native 30-second pass, Kling V3 motion control, Hailuo’s 6s/10s cheap rows, Cartesia, Inworld — none of those become Flow features because Omni 1.1 shipped.

Practical split:

• Need 1.1 extend, 360p drafts, or 1.1 first-last today. AI Studio, Agent Platform, Flow, or Gemini app extend. Export. Come back.
• Need Omni generate 4–10s or Omni retouch on this bill. Omni Video / Omni Flash Edit.
• Need Veo cinematic or Veo R2V. Veo cards, which Flow can also launch — still Veo, still not a studio.
• Need anything else. Change the row, not the vendor relationship with Google.

Do not migrate off Omni because Flow feels small. Do not migrate onto Flow because 1.1 landed. Honesty about the slate is the whole decision.

Caption and disclosure stay here regardless of door. Add captions to video. Article 50 disclosure if you publish a realistic synthetic to an EU audience. Flow will not typeset your safe area. The Gemini app will not store your caption style.

A one-week routing card

Monday: lock stills on a stills row if the product is the brief. Flux 2 Max is 6 credits, image, no duration.

Tuesday: Omni-shaped 6-second generate on Omni Video, from 29 credits. If you are still hunting and you have 1.1 access, 360p drafts on AI Studio instead, then upscale the keeper on 1.1.

Wednesday: jacket is wrong. Omni Flash Edit, from 50 credits. Do not re-roll the idea.

Thursday: the scene must continue. If you are already on 1.1 and the story is Omni, extend there (10s context, 10s steps, 40s cap). If you needed a native long take without a handoff, Seedance 2.5, 4–30s, 720p, from 34 credits (was 67). If you needed Veo’s extra beat, Veo extend.

Friday: captions, crop, label. Not Flow.

That week uses Google twice without living in Google. The access map is the point of 27 August: 1.1 is easy to reach if you already pay Plus / Pro / Ultra or already have AI Studio. Easy to reach is not “it replaced the catalog.”

When someone asks “do we have Omni 1.1?”, answer with the two slugs we have and the four Google doors. Then ask which control they actually needed. Most of the time it is generate or edit, and the Versely rows already do that job.

Run those rows after you sign up. Pick Edit or Omni Video. Do not wait for a 1.1 slug that is not in the published list.

FAQ

Is Omni 1.1 Flash a Versely model slug?

No. Published Omni rows are gemini-omni-flash-edit and gemini-omni-video. Google’s id is gemini-omni-1.1-flash, in AI Studio, Agent Platform, Flow (Plus / Pro / Ultra), and Gemini app extend (Google, 27 August 2026).

If I already use Flow for Veo, do I have 1.1?

Google says Omni 1.1 is in Flow for AI Plus, Pro, and Ultra as of that post. Flow is still a surface. You get 1.1 controls there. You do not get the rest of the catalog there.

Should we move the whole pipeline into AI Studio now?

Only if the pipeline is Omni 1.1 controls. AI Studio is a developer door. A week of captions, Seedance, Kling, and stills does not belong there. Use Studio for the 1.1 experiment. Ship from a roster.