The life of a request
From the visitor's browser to your origin and back.
A visitor requests a path
The browser asks for yourdomain.com/blog. Your DNS points the domain at Utilly.
Utilly matches the route
The path is looked up in your route table: /blog belongs to your WordPress origin.
Your origin serves the content
Utilly fetches the page from the origin over an encrypted connection, exactly as the platform produced it.
The response is delivered
The visitor gets the page from your one domain, with caching applied where it helps.
Everything passes through intact
Headers and cookies
Requests and responses pass through, so sessions, logins, carts, and consent banners keep working across every routed path.
Forms and query strings
Form posts, search parameters, and redirects behave the way your origin expects, because the proxy works at the HTTP level.
TLS on every route
Traffic is encrypted from the visitor to Utilly and from Utilly to your origins. Certificates are handled for you.
Your publishing workflows
The Webflow editor, wp-admin, and your deploy pipeline all stay exactly where they are. Utilly changes where content is served, not how it is made.
SEO-safe by construction
- One canonical host
- Content that used to live on subdomains is served from your main domain, so every backlink and ranking signal lands in one place.
- Automatic path mapping
- Internal pages and links are mapped to their subfolder paths, so visitors and crawlers see consistent URLs on your domain.
- Reversible by design
- Going live is one DNS change, and rolling back is the same change in reverse. Your origins are never modified.
Questions engineers ask
The details worth checking before you route production traffic.
What do I need to change on my origins?
Usually nothing. Every origin keeps its hosting and its publishing workflow. WordPress uses a small plugin to enable secure communication; other platforms just need a URL.
How does caching behave?
Utilly adds a caching layer in front of your origins. Cached pages are served without a round trip to the origin; everything else passes straight through.
What happens to headers, cookies, and forms?
They pass through. Sessions, logins, form posts, and query strings behave the way your origin expects, because the proxy works at the HTTP level.
How do I roll back?
Point your DNS back to its previous target and traffic flows exactly as before. Utilly never modifies your origins, so there is nothing else to undo.
Why is the architecture not documented in detail?
We keep our internals private on purpose. What we publish is the behavior you can verify from the outside: routing, caching, TLS, and rollback with a single DNS change.