Same box, new pizza. redirect.pizza has a new logo, a new color palette, and a redesigned website and app. Nothing changed about how your redirects work. Here's what did change.
The pizza slice stays. We'd never drop it. It's now a bolder, simpler wedge on our yellow tile, next to a deep plum that replaces pink as the main color. Plum carries the headings, buttons and hero sections, yellow is for the moments that matter, and there's a lot more white space in between. Calmer, easier to read, and still unmistakably us.
Every public page has been rebuilt on the new design: a new homepage, feature pages with live illustrations of automatic HTTPS and automatic DNS, a clearer pricing page (same plans, same prices), a dedicated enterprise section, and a cleaner reading layout for support articles and this changelog.
Inside your account the new colors carry over to headings, buttons, tables, charts and illustrations. We deliberately kept the layout as it was, so your redirects, domains and settings are exactly where you left them.
Everything under the hood. The edge network, your DNS records, the API, certificates and every redirect you've set up are untouched. There's nothing you need to do.
A redesign this size always leaves a few crumbs. If something looks off, tell us through the chat in the bottom right corner and we'll fix it quickly. And if you like the new look, we'd love to hear that too!
The API now covers more of what you can do in the dashboard.
You can update domain security settings, delete domains (including their sources and any redirects left empty), and filter redirect and domain lists with the same query search syntax used in the UI.
Team endpoints also expose and update settings such as name, summary emails, and security defaults. Updating team settings requires the new team:write scope.
We've improved the search functionality for redirects and domains, with better matching for exact fully qualified domain names (FQDNs), including paths. This makes it easier to quickly find the exact redirect or domain you're looking for, especially in larger configurations.
Users can now securely recover access to their account if they lose their two-factor authentication device. The new self-service recovery flow makes it possible to regain access without contacting support.
We've added a dedicated tags page where you can view all tags in your account, create them manually, and see which redirects and users are associated.
This makes it easy to set up tags ahead of time without first creating a redirect that uses the tag.
You can now use Accept-Language header values in dynamic destinations and rules. New variables include {acceptLanguage.raw}, {acceptLanguage.primary}, {acceptLanguage.language}, {acceptLanguage.region}, and {acceptLanguage.q}, making it easy to steer visitors based on their preferred language.
We've added support for SAML Single Logout (SLO). Users can now be signed out through both Identity Provider (IdP)-initiated logout and Service Provider (SP)-initiated logout, providing a complete logout experience across connected applications.
Redirects are no longer limited to ports 80 and 443. We now accept incoming traffic on additional standard HTTP and HTTPS ports, making it easier to redirect applications and services running on custom ports.
Supported HTTP ports: 80, 8080, 8880, 2052, 2082, 2086, 2095.
Supported HTTPS ports: 443, 2053, 2083, 2087, 2096, 8443.