Keep deploying on Replit. Serve from your domain.
replit, served from the domain you already rank on
- The deployment is the origin
- Autoscale, Static, or Reserved VM: Utilly only needs the replit.app URL. The deployment settings, scaling, and secrets stay exactly where they are.
- No domain linking on Replit
- No A record, no TXT verification, no certificate to wait on. Your domain points at Utilly, and TLS is handled for every route.
- Public pages build your domain
- A directory, a data tool, a generator: if strangers should find it, its links belong on yourdomain.com, not on a subdomain.
Live in four steps
Replit keeps hosting. Utilly does the routing.
Deploy on Replit
Publish the app as an Autoscale, Static, or Reserved VM deployment. Replit gives it a replit.app URL; leave the domain linking screen alone.
Connect the origin
Add the replit.app URL to Utilly as an origin, alongside the site that serves the rest of your domain.
Map and preview /app
Choose the path, then exercise the app on the preview: pages, forms, and any request the app makes to its own backend.
Go live
One DNS change. The marketing site keeps /, Replit serves /app, and each new deployment shows up there.
Replit custom domain FAQs
Why can Replit not serve the app at a path of my domain?
Replit links a domain or subdomain to a deployment with A and TXT records, which hands the whole host to Replit. Serving yourdomain.com/app next to a site on another platform requires a reverse proxy that owns the domain and routes that one path to the deployment.
Do I link the domain in Replit as well?
No. Your domain points at Utilly, and Utilly fetches from the replit.app URL. You skip the domain linking flow in Replit entirely, including its certificate steps.
Which deployment types work?
Any deployment with a public URL: Autoscale, Static, and Reserved VM. Scheduled deployments have no web endpoint, so there is nothing to route.
My Replit app has its own backend. Does it still work?
Requests the browser sends to a different host are unaffected. Requests to your own domain are routed by path, so an app that calls its backend with root-relative URLs should be verified in preview, and a base path setting on the app side keeps everything under /app cleanly.
Does it work with Replit Agent projects?
Yes. Whatever built the app, the deployment ends up at a replit.app URL, and that URL is all Utilly needs.
What should I check in preview?
Deep links, a full reload on an inner page, form submissions, and any API call the app makes to itself. Those are the places a subfolder can surprise you, and the preview exists so you catch them first.