Search for Veo on Google’s side and you land on a confusing spread of addresses: deepmind.google/models/veo, aistudio.google.com, Vertex AI on Google Cloud, and a rotating cast of labs.google experiments like Whisk and Opal. They all mention the same model, but they are not the same thing — some are showcases you cannot generate from, some are developer consoles that bill through an API key, and one is an enterprise cloud product.
This guide maps each surface: what DeepMind’s Veo pages are for, how Google AI Studio and the Gemini API give developers Veo access, where Vertex AI fits, and what the Labs experiments actually do. The pattern to notice up front is that every one of these doors is built for a specific audience — researchers, developers, or enterprises — and none of them is simply a website where you type a prompt and download a clip.
If that last part is what you came for, the honest answer is that you do not need any of them. Veo AI runs the same Veo model family — Veo 3.1 and Veo 4 among 40+ models — in a normal browser tab, with credits instead of API keys or cloud billing. We will cover both routes so you can pick the right one.
The Google surfaces that mention Veo — at a glance
Four different Google properties show up for Veo searches, and each answers a different question. Before digging into any of them, here is the map:
| Surface | What it is | Can you generate there? |
|---|---|---|
| deepmind.google/models/veo | DeepMind’s research and showcase pages for the Veo models | No — it links out to other products |
| aistudio.google.com | Google AI Studio: the developer console for the Gemini API | Yes — as a developer, billed via API usage |
| Vertex AI (Google Cloud) | Enterprise machine-learning platform where Veo is a managed model | Yes — within a Google Cloud project |
| labs.google (Flow, Whisk, Opal…) | Google Labs experiments that use Veo under the hood | Varies — consumer tools, subscription-gated |
| Veo AI (this site) | Browser studio running Veo 3.1, Veo 4 and 40+ other models | Yes — credits, no API key or cloud account |
DeepMind’s Veo pages: research showcase, not a studio
Google DeepMind is the research lab that builds the Veo models, and deepmind.google/models/veo is where it presents them — capability write-ups, sample reels, safety notes, and announcements as new versions ship. Searches like "deepmind veo 3", "veo3 deepmind", and the full URL "https://deepmind.google/models/veo/" all point at this showcase.
What the page is not: a generation surface. There is no prompt box on DeepMind’s site. It exists to document the research and then route you to the products that expose the model — the Gemini app and Flow for consumers, AI Studio and Vertex AI for developers. If you arrived at DeepMind’s Veo page hoping to make a video, you were always going to be sent somewhere else; the only question is which door fits you.
Google AI Studio: Veo for developers via the Gemini API
Google AI Studio at aistudio.google.com is the free developer console for the Gemini API. It is where you sign in with a Google account, create an API key, and experiment with Google’s models — including video generation with Veo, which is why queries like "google ai studio veo 3" and "aistudio.google.com/generate-video" lead here. You can try prompts in the browser, then take the same request into your own code through the API.
The crucial detail is how it is paid for. AI Studio itself is a console, but Veo generation through the Gemini API is billed usage — priced per second of generated video, charged against the billing account attached to your key. There is no flat consumer subscription here: it is metered developer infrastructure, which is exactly right if you are building an app and exactly wrong if you wanted to make a handful of clips. Earlier model versions surface here too, which is why "google ai studio veo 2" searches still resolve — but new keys get routed to current Veo releases.
- Audience: developers integrating video generation into their own products.
- Access: Google account → AI Studio → create an API key.
- Cost structure: metered API billing, priced per second of generated video.
- Good for: prototyping, then shipping Veo inside your own app.
- Not for: casual generation — there is no credit pack, only usage billing.
Vertex AI: the enterprise route on Google Cloud
Vertex AI is Google Cloud’s machine-learning platform, and it is where organisations consume Veo with enterprise controls: IAM permissions, quota management, data-residency options, and billing that flows through an existing Google Cloud account. Searches for "vertex ai veo 3" and "google cloud vertex ai veo 3" are usually teams evaluating exactly this.
Functionally it exposes the same model family as the Gemini API, wrapped for production workloads. If your company already runs on Google Cloud and needs Veo inside a governed pipeline — batch generation, service accounts, audit trails — Vertex is the intended door. For an individual, setting up a cloud project, enabling billing, and navigating quotas is heavy machinery for the job of making a video.
Labs experiments: Whisk, Opal, and friends
Google Labs at labs.google is the public playground where experimental products ship early, and several of them touch Veo. Flow is the big one — the AI filmmaking tool, covered in our dedicated Flow guide. Whisk is an image-remixing experiment whose Whisk Animate feature turns still images into short video clips using Veo, which is what "whisk animate", "whisk veo 2" and "whisk veo 3" searches are about; animation there is gated behind Google’s paid AI plans. Opal is a different kind of experiment — a Labs tool for building small AI mini-apps without code — and when people search "google opal + veo" they are usually wondering whether Opal workflows can call video generation; it is an app-building surface, not a video product in itself.
The common thread: Labs products are experiments. They change shape, move behind subscription tiers, roll out US-first, and sometimes disappear. "Labs google veo 3" is less a destination than a category — Veo keeps appearing inside whatever Labs is testing this quarter.
Developer doors vs. just generating in a browser
Here is the honest pivot. Every Google surface above is a door built for someone: DeepMind for reading about the research, AI Studio and Vertex for building on the API, Labs for testing experiments inside Google’s subscription ecosystem. If you are a developer shipping a product, AI Studio is genuinely the right place to start, and our Veo API guide covers that path in more depth.
But most people searching these terms are not integrating an API — they want to type a prompt and get a clip. For that, Veo AI runs the same Veo model family in a normal browser: Veo 4 and Veo 4 Fast, Veo 3.1 and Veo 3.1 Fast, and Veo 3.1 Lite, next to Sora 2, Kling, Hailuo, Wan, Seedance and some forty other models. No API key, no cloud project, no per-second invoice at month’s end — you see the credit cost before each generation, new accounts start with free credits, and clips come out in 720p or 1080p, 16:9 or 9:16, with native audio and watermark-free downloads.
| AI Studio / Vertex AI | Veo AI | |
|---|---|---|
| Built for | Developers & enterprises | Anyone with a browser |
| Setup | Google account, API key or cloud project | Sign up, start generating |
| Billing | Metered API usage, per second of video | Credits — cost shown before you generate |
| Models | Veo family via Gemini API | Veo 4, Veo 3.1 + Sora 2, Kling, 40+ more |
| Controls | Code-level API parameters | Image-to-video, keyframes, reference images, negative prompts, extension |
| Output | Returned via API | 4–8s clips, 720p/1080p, clean downloads |
Which door should you take?
Pick AI Studio if you are a developer who wants to prototype against the Gemini API and ship Veo inside your own software. Pick Vertex AI if you are doing the same thing inside an organisation that already lives on Google Cloud. Read DeepMind’s pages when you want the research story, and watch Labs if you enjoy testing Google’s experiments as they ship.
Pick Veo AI when the goal is the video itself. The model family is the same; the difference is that everything between you and the output — keys, quotas, cloud billing — is replaced by a prompt box and a visible credit price. You can be rendering your first Veo 3.1 clip in the time it takes to create an API key.