Where is Gemini Omni 1.1 Flash? Google's named partners and Sume

Google's Omni 1.1 Flash launch post names four products that already use the model in production: Adobe Firefly, Figma Weave, Runway and GMI Cloud. If you want the model without a design app around it, you can call it from Google's API, or from Sume as gemini-omni-flash-1.1, which adds job ids, idempotent submits and a billing record.

Everything about Google here comes from its launch post, the pricing page and the deprecations page, all read on 2026-10-02. I did not read the four partners' own pages, so I say nothing about their prices or limits.

What does Google say about the model and its users?

The post says Omni 1.1 Flash was released on August 27, 2026 as a production-ready model, available in Google AI Studio, the Gemini Enterprise Agent Platform and Google Flow for AI Plus, Pro and Ultra subscribers. New controls are scene extension up to 40 seconds in 10-second steps, first and last frame control, a 360p draft mode that is up to 60 percent faster at a third of the cost, 1080p or 4K output, and up to three seconds of video as a reference. Adobe Firefly, Figma Weave, Runway and GMI Cloud are listed as current production users.

The deprecations page shows gemini-omni-1.1-flash released August 27, 2026 with no shutdown announced. It also lists the Veo 3.1 preview ids, which end on October 22, 2026, with that model named as the replacement.

What does the Gemini API charge?

The pricing page lists video output at $17.50 per million tokens for Omni Flash, paid tier only, at 5,792 tokens per second of 720p video, which is roughly $0.10 per second. For comparison it lists Veo 3.1 at $0.40 per second at 720p and 1080p, Fast at $0.10 for 720p and $0.12 for 1080p, and Lite at $0.05 for 720p and $0.08 for 1080p, all with default audio and charged only when the video generates successfully.

What does Sume add on top?

The router takes text, an image, reference images and clips, or a source video for edit, and runs each as a job. Submits are idempotent, so a retry does not bill twice, and the status route tells you when a result is ready. Sume says nothing in its docs about being the same price as Google, and it is not: it lists the provider price times 1.25.

What you give up is any Google-side surface. There is no Flow canvas, no Vids and no Gemini app. Sume has an API and an agent, and the call below is the whole integration.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: partner-compare-001" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "A tea cup steams on a windowsill at dawn. Quiet room tone.",
    "duration": 5,
    "resolution": "360p",
    "aspect_ratio": "16:9",
    "mode": "async"
  }'

How should I choose?

Pick a partner app when you want its editor and are happy with its pricing. Pick Google's API when you already run on Google Cloud. Pick Sume when you want to run the same model next to others in one catalog, with job ids you can store. Start with a 360p draft to check the idea before you pay for more.

What would I check on any partner page?

Before you build on a partner, read its own page for four things: the model version it runs, the resolutions and clip length it exposes, what it charges per second or per credit, and whether it has an API. Google's launch post only says these products use Omni 1.1 Flash in production; it says nothing about how each one prices or limits it.

Also check what comes back. A design app returns a clip in its editor. An API returns a file URL and a job record. Know which one your workflow needs before you compare prices, since a lower number in an app is not comparable to a per-second rate in an API.