Wildcard Origin Patterns
Pro and Enterprise plans now support wildcard origin patterns to match multiple subdomains with a single configuration.
Use Cases
Wildcard patterns are ideal for:
- Multi-tenant SaaS applications — Match all customer subdomains (
*.myapp.comcoverscustomer1.myapp.com,customer2.myapp.com, etc.) - Regional deployments — Support multiple locations with one pattern (
*.example.comcoverseu.example.com,us.example.com, etc.) - Development environments — Cover all staging and preview deployments at once
New Pattern Format
All plans now use a simplified origin format:
- Domain:
example.com— matches both HTTP and HTTPS - With port:
localhost:3000— for development servers
Pro and Enterprise plans additionally support:
- Wildcard:
*.example.com— matches all subdomains
Automatic Migration
Existing origins have been automatically converted to the new format:
- https://example.com → example.com
- https://www.example.com → www.example.com
No action required—your applications continue to work.
Benefits
- Simpler configuration: No need to enter the scheme (https://)
- Scheme-agnostic: Both HTTP and HTTPS requests match the same pattern
- Wildcard support (Pro/Enterprise): One pattern covers all subdomains