Keep your hostname
Send every path on your verified domain to an origin pool while keeping your brand in the address bar.
Use one hostname for a pool of servers. Route traffic by priority, region, origin load or latency. Combine country and site pools under one hostname with failover and loop detection.
Managed setup for production websites, APIs, and company intranets. Use your own domain or a Zogy subdomain.
Request managed setupSend every path on your verified domain to an origin pool while keeping your brand in the address bar.
Use priority, weighted routing, round robin, client affinity or regional chains. Retries and redirect loops are bounded.
Connect approved internal origins and let employees sign in with your company identity provider.
Monthly base rates include one hostname, two origins and TLS. Extra hostnames each include two origins. The hostname and origin add-ons are prorated hourly.
Load balance a Zogy subdomain or a verified domain you control.
Route internal sites and APIs through an outbound tunnel. Employees sign in with your company identity provider.
Zogy charges by hostname, origin and request volume. Your identity and network providers may charge separately. Grasany confirms a quote before activation.
The estimate assumes all selected hostnames and origins are active for the full month. Origin retries count as part of the incoming request.Managed setup supports a Zogy subdomain or a hostname you control. DNS verification and TLS must be complete before you can send traffic. For a custom domain, visitors stay on your hostname as Zogy forwards requests to your servers.
Eligible read requests can retry on a network error, timeout, or 502, 503 or 504 response. Writes and WebSocket handshakes are forwarded once. Set a standby origin, choose a routing mode for each path, or group several sites by country.
Cycles between routing groups are rejected during setup. Guarded mode stops repeated same-host redirects on GET and HEAD requests. Redirects that set cookies and redirects to external sites go back to the browser.
Run an outbound connector in your network. During onboarding, register each internal HTTP service and configure an employee sign-in policy for the frontend hostname. Your origin servers can stay on private addresses. The initial intranet offering is for web applications and APIs.
Request logs record the hostname, method, route label, status, chosen origin, retry attempts and time to response headers. URL queries, bodies, cookies and authorization headers are excluded.
Each active hostname includes two origins. An origin used by multiple path rules on the same hostname counts once. The estimator asks for the total number of origins beyond the two included on each hostname.