Application routing for domains, HTTPS, redirects, and access rules

Wodby-generated technical domains provide immediate browser access without waiting for DNS changes. Custom routes connect your own domains to the appropriate app service and port, while a primary route identifies the main application address.

• Expose only the services and ports that need external access.
• Use Wodby technical domains for development and staging access.
• Attach custom domains for production or branded environments.
• Publish supported TCP or UDP ports for services that need non-HTTP access.

Wodby provisions and automatically renews Let's Encrypt certificates for supported technical and custom routes. Paid organizations can instead upload a custom TLS certificate and reuse it across every route hostname that it covers.

When a custom certificate is selected, Wodby shows only active certificates whose DNS names match the route hostname. Certificate status, usage, and expiration remain visible, while staged warnings help administrators replace uploaded certificates before they expire.

For more certificate-focused details, see the SSL and TLS feature page.

Redirect alternate domains or paths to the preferred address, require HTTP basic authentication at app, service, or route scope, and apply route settings without changing application code.

• Create permanent or temporary redirects for domains and paths.
• Redirect HTTP traffic to HTTPS.
• Mark lower environments as no-index.
• Set request body size limits for upload-heavy services.
• Use session affinity when a service requires sticky traffic.
• Rewrite paths when upstream services expect a different URL shape.
• Enable HSTS on HTTPS routes, optionally including subdomains.
• Apply HTTP basic authentication at app, service, or route scope.

For identity-aware or private-network access, use Private app access to protect the complete application or selected HTTP endpoints through Cloudflare or Tailscale.