Google AI Studio Finally Gives Deployed Apps Clean, Shareable URLs
Google AI Studio now lets you give deployed apps a clean atelier.ai.studio URL instead of a random Cloud Run slug
- Custom URLs live: Google AI Studio apps can now get a clean
atelier.ai.studioaddress instead of a random Cloud Run slug. - Set at publish time: Choose your custom URL when clicking Publish in Build Mode, no DNS or SSL setup required.
- Free tier included: Up to 2 apps deploy for free with no credit card via the Google Cloud Starter Tier.
- Full stack backed by Cloud Run: Apps auto-scale to traffic and scale to zero when idle; API keys stay server-side and secure.
- Broader context: Part of AI Studio's ongoing push from prototype tool to full product platform, following I/O 2026 additions like Android app support and Workspace integrations.
- Try it: Build at aistudio.google.com and see a live example at atelier.ai.studio.
If you've ever deployed an app from Google AI Studio and then tried to share the link, you know the problem. The URL you get looks something like https://burning-man-animal-cuddle-614365371127.us-west1.run.app/. It's live, it works, but it's not exactly something you'd put on a landing page. Google just fixed that.
The team announced custom URLs for AI Studio deployed apps, giving them a permanent home under the atelier.ai.studio domain. Instead of a machine-generated Cloud Run slug, your app gets a clean, memorable address you choose yourself, set at publish time.
The gap this fills
Until now, the path from prompt to deployed app in AI Studio was impressively short, but the finish line was a bit rough. AI Studio lets you deploy full-stack applications directly from Build Mode, providing a fast path from prototype to a managed, scalable production environment. The infrastructure side was handled. The identity side was not.
The workaround was either living with the ugly URL or going through a multi-step process of pushing to GitHub, importing into Vercel or Cloud Run, and wiring up DNS records manually. If you've never connected a Google Cloud Run service to a third-party registrar, the "DNS Dance" can be confusing. Custom URLs on