Google AI Studio now lets builders on paid Cloud projects buy and attach a custom domain from the Publish panel, on top of the free yourapp.ai.studio subdomains we covered in July 2026. The change matters for portfolio links, client demos, and Gemini API apps that outgrew anonymous Cloud Run URLs.
Official steps live in Google's deploying guide and the linked Custom domains in Google AI Studio doc.
What changed versus July subdomains
| Option | Tier | URL shape | Purchase path |
|---|---|---|---|
| Free subdomain | Starter or paid | https://name.ai.studio | Pick name in Publish; first-come |
| Custom domain (new emphasis) | Paid project only | https://example.com | Buy in Publish via Cloud Domains |
Starter Tier still caps two published apps, one region, and no billing. When you need a third app, custom domain, or higher quotas, Google converts the project to a standard billed Cloud project without deleting existing deploys.
API adapter concept for Google AI Studio custom domain and Cloud DNS routing
What Google automates in the Publish flow
Per the deploying documentation:
- Cloud Domains registration for the name you choose inside AI Studio.
- Cloud DNS routing to the Cloud Run service behind your app.
- Managed SSL certificate issuance.
- Dual URLs — your app keeps its
ai.studiosubdomain even after you addexample.com.
Deletion and unpublish rules remain strict: unpublishing frees subdomains globally, and deleting an app forces a choice on whether to keep paying for a domain subscription.
Pricing and quota traps
Google cites roughly $12/year registration depending on TLD plus Cloud DNS zone fees from $0.20/month before query charges. Domain purchases are non-refundable once registered, per third-party summaries of the same docs.
Builders often underestimate Gemini API usage on top of hosting. Our Gemini API docs preview and cancelled mobile app post stress that hosting can stay cheap while inference scales with traffic.
Workspace accounts may fail Starter Tier eligibility; Google's docs say support cannot override eligibility. That pushes many teams straight to paid projects—which is also the only path to custom domains.
Step-by-step for a paid project
- Open the app in Build mode and click Publish.
- Confirm or attach a billed Google Cloud project with Editor/Owner access (forum posts warn Viewer-only projects cannot map domains).
- Expand Custom domains, search an available name, and complete Cloud Domains checkout.
- Wait for DNS + SSL provisioning; Google keeps the
ai.studioURL active in parallel. - Document who owns the domain subscription if multiple teammates publish.
For Howie scheduling acquisition watchers, custom domains are the deploy polish layer; agent features are separate SKUs.
Android download chatter
Aggregators in November 2026 claimed U.S. users can download AI Studio-built Android apps to devices. Google did not mirror that headline in the deploying doc we fetched. Treat mobile install as verify in AI Studio release notes before promising clients a store-less APK flow.
Search intent: "buy domain AI Studio" vs July free URLs
Readers upgrading from our July subdomain guide usually ask three things:
- Do I lose
name.ai.studio? No — Google keeps both URLs live. - Can Starter Tier upgrade in place? Yes — conversion preserves apps, but triggers billing.
- Who owns the domain if I leave Google? Domains bought in-product follow Cloud Domains transfer rules; plan registrar portability before marketing a
.comheavily.
Troubleshooting permission errors
The Google AI Developers Forum documents a common failure: Viewer access on the backing Cloud project blocks custom domain mapping. The fix is remix/publish to a project where you hold Owner or Editor.
Symptoms and fixes:
| Symptom | Likely cause | Fix |
|---|---|---|
| Greyed-out custom domain | Starter Tier | Upgrade project billing |
| "Permission denied" on DNS | IAM role | Move app to owned project |
| SSL pending for hours | DNS propagation | Wait; verify Cloud DNS zone |
| Name taken on ai.studio | First-come conflict | Pick alternate subdomain |
Security and brand considerations
IAM and domain credentials concept for custom AI Studio domains
Custom domains raise phishing risk if builders impersonate banks or government agencies. Google routes trademark complaints through its Legal Troubleshooter for abusive ai.studio names; .com purchases still require your compliance review.
Pair domain launches with temporary chat retention policies if user data flows through Gemini backends—hosting is only the front door.
Comparisons for builders
- Vercel / Netlify custom domains — cheaper if you already host outside Google; AI Studio optimizes one-click Gemini + Cloud Run.
- Cloud Run alone — more control, more YAML; AI Studio targets vibe-coded apps from Build mode.
- Amex intent frameworks — unrelated to DNS, but relevant if your published agent can pay; scope domains separately from payment permissions.
What to do this week
- Upgrade one pilot app to a paid project and benchmark monthly Cloud Run + API cost before buying a domain.
- Reserve critical
ai.studionames early even if you plan a custom TLD later. - Snapshot DNS records after setup for disaster recovery if you delete and recreate apps.
- Link domains in README and portfolio using HTTPS-only canonical URLs for SEO.
Starter Tier versus paid: decision tree
Choose Starter Tier when you are prototyping two public demos, can accept name.ai.studio, and fit Google's eligibility rules (personal Gmail accounts with activity history, no conflicting billing accounts).
Upgrade to paid when you need custom domains, more than two live apps, multi-region Cloud Run, or Gemini quotas beyond Starter caps.
Remix workflow matters for teams that started on Starter but hit walls: Google preserves published URLs when converting, yet domain purchases still require IAM-correct projects—plan one owner account early.
Integrating custom domains with CI
Advanced teams sync AI Studio exports to GitHub and deploy outside Studio. Custom domains bought in-product still route to Cloud Run services Google manages; if you redeploy from CI, verify DNS records still target the active revision. Our Gemini API docs preview post notes Docs MCP workflows that may reference deployed URLs in README badges—update those badges when domains change.
Cost model example (illustrative, not a quote)
Imagine a hackathon winner with 500 daily users, short sessions, and Gemini Flash calls:
- Cloud Run might remain inside free tiers depending on region.
- Gemini API often dominates the bill once traffic spikes.
- Custom domain adds fixed dollars atop variable inference.
Builders should run Google's pricing calculator after the first week of telemetry, not before buying a vanity TLD.
Workshop tie-in
Shipping a polished domain helps AI Studio Android experiments and classroom demos alike. explainx.ai workshops cover Gemini API budgeting that pairs with custom domains.
Pricing and quotas verified against Google docs on November 18, 2026.
Field guide: publishing checklist before sharing a custom domain
Walk through this sequence on a paid project before tweeting a new .com:
- Publish to Cloud Run from Build mode and confirm the default URL loads.
- Claim or verify
name.ai.studioso squatters cannot hijack your brand string. - Purchase the custom domain only after IAM roles are correct.
- Wait for SSL issuance; test both HTTP redirect and HTTPS cert chain.
- Add canonical links in your README and OpenGraph tags if you export code.
- Monitor Gemini quota dashboards for a week; domain traffic spikes can surprise teams who only tested with founders.
- Document who pays for domain renewal—students forget annual renewals more often than they forget API keys.
How this fits Google's broader agent push
Custom domains beautify Gemini-powered micro-apps, the same week Google pitched Gemini Tasks and Labs acquisitions. None of those products require a custom domain, but go-to-market teams want URLs that survive screenshots in slide decks.
Migration scenarios from other hosts
Teams moving from Vercel or Netlify should decide whether AI Studio remains source of truth:
- If yes, keep editing in Build mode and treat Git sync as backup, not primary deploy.
- If no, export ZIP/GitHub, run RoamerHost-style hosting per third-party guides, and do not buy domains in AI Studio unless DNS will stay on Google Cloud.
Misaligned DNS causes week-long outages when students graduate and lose access to the Google account that owns Cloud Domains.
Educator and newsletter use cases
Newsletter operators linking to interactive Gemini demos benefit from memorable domains more than CLI hackers do. Pair custom domains with explainx.ai newsletter signup CTAs thinking: if readers bookmark your demo, SSL renewal failures become brand incidents—set calendar reminders.
FAQ alignment with Search Console intent
Queries like "how to deploy Google AI Studio app" and "custom URL AI Studio" overlap. This post targets buyers ready to pay for domains; the July post targets free subdomains. Interlink both so Google sees clear intent separation rather than cannibalized rankings.
Keep a changelog when Google edits Cloud Domains pricing footnotes—domain SKUs change more often than Gemini model names.
Bookmark Google's Custom domains in Google AI Studio child doc for DNS troubleshooting screenshots your team will need during launch week.
