Your vibe-coded app.
Your main domain.
Lovable, Bolt, Replit, and v0 publish to their own URLs, or at best a subdomain. Utilly serves the app at yourdomain.com/app instead: managed routing, TLS, and caching in front of whatever your builder hosts. Live with one DNS change.
7-day free trial · No credit card required
The builder hosts it. Your domain serves it.
ai-built apps, served from the domain you already rank on
- Nothing moves off the builder
- The app stays hosted and deployed by Lovable, Bolt, or Replit. Utilly points at the published URL, and every time you publish again the path on your domain updates with it.
- The marketing site stays where it is
- Webflow, WordPress, or Framer keeps serving /. The app takes /app. Neither platform has to know the other exists.
- Search authority lands in one place
- A public tool or landing page earns links. On a path, those links build your main domain instead of a subdomain, or a builder host shared with every other project on the platform.
The layer in front of the app
Utilly is not a hosting platform, and it does not run your code, your database, or your auth. Your builder does that and keeps doing it. Utilly owns the domain in front of the app: the part no builder can give you on a path of a site you already run.
Routing table
Each path of your domain maps to one origin: / to the marketing site, /app to the builder. Add or change a route in the dashboard, with no code and no deploy.
TLS on every route
Certificates for your domain are issued and renewed for you, and traffic is encrypted from the visitor to Utilly and from Utilly to the builder.
Caching in front of the builder
A caching layer sits in front of the published app, so repeated page loads are served without a round trip to the builder's hosting.
Preview and rollback
Click through the app on its new path before it is public. Going live is one DNS change, and rolling back is the same change in reverse.
Live in four steps
The builder keeps shipping. Utilly does the routing.
Publish in your builder
Ship the app the way you already do. Lovable, Bolt, Replit, and v0 each give it a published URL; that URL is all Utilly needs.
Connect the origin
Paste the published URL into Utilly as an origin, next to the Webflow, WordPress, or Framer site that serves the rest of your domain.
Map and preview the path
Assign the app to /app, /tools, or any path you like, then click through it on the preview before anything is public.
Go live
One DNS change. The marketing site keeps serving /, the app starts serving its path, and rollback is the same change in reverse.
Pick your builder
Each platform publishes a little differently. These pages cover what to point Utilly at and what to check in preview.
Building with v0, Cursor, or Claude Code and deploying to Vercel or Netlify? Nothing changes: point Utilly at the deployment URL and map the path the same way.
When a subdomain is still the right call
Login-only dashboards
If every page sits behind sign-in, nothing there will rank, and app.yourdomain.com costs you nothing.
Internal tools
Ops dashboards and team utilities belong off the public domain entirely, on a subdomain or behind a VPN.
Staging and experiments
Anything you might delete next month should not earn links on the main domain first.
Everything else, meaning the tools, calculators, directories, and landing pages you built precisely so strangers would find them, belongs on a path. The full argument is in subdomain vs. subfolder for SEO.
Vibe-coded app routing FAQs
Do I have to export the code or move hosting?
No. The app keeps running on the builder that made it, and you keep publishing there. Utilly points at the published URL and routes a path of your domain to it, so every new publish shows up at that path.
Does the app keep working under a path like /app?
Internal pages and links are mapped to the subfolder path automatically, and the preview lets you click through the whole app before you switch DNS. If your builder offers a base path setting, matching it to the subfolder is a sensible extra step for apps with many client-side routes.
What about Supabase, Firebase, or a separate API?
Calls the app makes to another host are unaffected; the browser still sends them straight to that host. Only page requests to your domain pass through Utilly. Apps that call their own backend on the builder host should be verified in preview like any other route.
Do I connect my domain in the builder as well?
No. Your domain points at Utilly, and Utilly fetches the app from the URL the builder already publishes to. Nothing about the domain needs to be configured in Lovable, Bolt, or Replit.
Is a subfolder always better than a subdomain for an app?
Only when the app should rank. Public tools, calculators, directories, and landing pages earn links, and those links should build your main domain. A login-only dashboard can stay on app.yourdomain.com; nothing is lost there.
What does it cost?
Plans start at $29 per month with a 7-day free trial and no credit card required. Routing an app into a subfolder counts as one route on one domain, the same as a blog or a docs site.