Netlify Redirects vs RedirHub (2026): Pricing, Migrations & Best Fit
Netlify suits redirects that belong to a Netlify-hosted app; RedirHub suits retired domains, cross-platform migrations and URL mappings that live outside one application.
We build RedirHub. We point out where Netlify Redirects is the better buy, and how to check against your own setup.
The short answer
Choose RedirHub if
- Redirects are infrastructure in their own right: retired domains, cross-platform migrations or individually mapped URLs
- You need their own workspace, CSV/API workflow and capacity model outside the application
Choose Netlify if
- The redirects belong to a Netlify-hosted app
- Developers already own its routing and deployment configuration
- You need application-edge conditions such as country, language, cookie or role-based routing
Which product fits your job#
Keep app redirects next to a Netlify project
Netlify's documented routing model keeps redirects and rewrites in _redirects or netlify.toml, evaluated at its CDN edge.
Redirect multiple domains assigned to one Netlify site
Netlify supports domain redirects for domains assigned to a site and automatically provisions HTTPS for custom domains.
Run country-, language-, cookie- or role-based routing for a Netlify app
Those conditions are first-class options in Netlify's redirect engine.
Move thousands of changed URLs and manage the mapping separately from the application
RedirHub treats each source-to-destination migration mapping as managed-link capacity and provides CSV import/export outside an application repository.
Operate retired domains and redirects across several sites or hosting stacks
RedirHub is dedicated redirect infrastructure with domain and managed-link capacity that scale independently.
The strongest reason to choose Netlify is not that it is a cheaper redirect SaaS. It is that redirects are already part of the platform where your application is built and delivered. The strongest reason to choose RedirHub is organizational separation: the redirects need their own lifecycle, capacity model and workspace rather than being application configuration.
Netlify redirects are part of a web development platform#
Netlify currently positions itself as a web development platform that takes projects from AI tools or Git to global deployment. Its edge product explicitly describes redirects, proxies, access control and A/B tests as part of the application's edge configuration.[1]
That context matters. In Netlify's documented static-routing workflow, redirect and rewrite rules live in a site's _redirects file or netlify.toml. Netlify serializes those rules and evaluates them at CDN edge nodes.[2]
For a frontend team already shipping the site on Netlify, this is a feature, not a limitation. Redirect changes can follow the same version control, preview and deployment discipline as the rest of the application.
Our call
If the redirect rules logically belong to one Netlify application and developers own them, keep them in Netlify unless another operational requirement gives you a reason to separate them.
Website migrations and large redirect sets#
A migration can look very different depending on whether the URL structure stays predictable.
Netlify supports individual rules, placeholders, wildcards, query matching and conditional routing. Its documentation says that if you need 10,000 redirects or more, you should use wildcards or placeholders as much as possible, and consider Edge Functions for more complex setups. That is guidance about how to structure a large ruleset, not a published 10,000-rule plan limit.[2]
RedirHub uses a different model. An individually configured website-migration source-to-destination mapping is one managed link. Core starts at $49/month for 25 domains and 2,500 managed links. If you need 10,000 managed links and no more than 25 domains, the current Core capacity step is $89/month.[3]
Sizing a 10,000-mapping migration? See what your current setup would cost on RedirHub.
Calculate your setupThat makes RedirHub easier to size when the job is explicitly "we have a spreadsheet of old URLs and new URLs, and this mapping should remain independent of the application." CSV import/export is available on all plans, so the redirect estate can be reviewed and managed as data rather than copied into application routing configuration.
Our call
Netlify is a strong migration choice when the redirect logic belongs to the Netlify site and can be expressed cleanly in its routing model.
RedirHub becomes more useful when the mapping itself is the long-lived operational asset.
Pricing: do not compare the plan prices as if they buy the same thing#
Netlify does not sell a redirect-only plan. Its current credit-based pricing covers deployments, compute, bandwidth, web requests and other platform usage.[4]
| Plan | Published monthly price | Included usage |
|---|---|---|
| Netlify Free | $0 | 300 credits/month |
| Netlify Personal | $9 | 1,000 credits/month |
| Netlify Pro | $20 | Starts at 3,000 credits/month; unlimited members |
| RedirHub Core | $49 | 25 domains, 2,500 managed links, unlimited requests |
On Netlify, web requests consume 2 credits per 10,000 requests, and the definition explicitly includes redirects. The same credit pool is also used by other metered platform resources. For example, one million web requests would consume 200 credits before considering bandwidth, production deploys, compute or other usage.[4]
RedirHub does not meter redirect traffic by request count. Its paid plans use domain capacity and managed-link capacity, which can be expanded independently.
That means the cheap-looking comparison is also the fair one: if you already host the site on Netlify and have enough credits, a modest redirect set may have little or no incremental software-plan cost. Paying separately for RedirHub only makes sense when the dedicated redirect workflow itself has value.
Our call
Do not buy RedirHub just to duplicate a routing job Netlify already handles well.
Buy dedicated redirect infrastructure when ownership, portability, migration mapping or domain operations need to be separated from the web application.
Routing behavior: Netlify is broader inside the application#
Netlify's redirect engine supports 301 and 302 redirects, 200 rewrites/proxies, query matching and conditions including country, language, role and cookie presence. Its current documentation says 307 is not supported and recommends 302 for temporary redirects.[5]
RedirHub supports 301, 302, 307 and 308 redirects, path forwarding and query-parameter forwarding. The products are therefore not simply "Netlify has fewer redirect features" or "RedirHub has more." Netlify has particularly strong application-edge conditions; RedirHub is built around persistent redirect and link management.
For teams evaluating both, the better question is where the routing logic should live.
Domains and HTTPS#
Netlify can add domain redirects for multiple domains assigned to a site, and it offers free HTTPS on Netlify sites. When you add a custom domain, Netlify automatically provisions a Let's Encrypt certificate and renews it as needed.[7][6]
RedirHub also includes automatic HTTPS. The difference is not whether either product can serve a secure redirect. It is whether the redirecting domain belongs naturally to a Netlify project or should be managed in a separate redirect workspace.
A retired brand portfolio is a good example. If ten old domains exist only to send traffic somewhere else, attaching them to application projects may be less natural than managing them as a redirect estate. If the domains are aliases of one Netlify site, Netlify's own domain management may be the simpler option.
Operational ownership matters more than the feature checklist#
Netlify's documented workflow is developer-oriented: routing rules live with the site configuration, and Git-integrated projects can ship changes through the same deployment process as application code. Netlify also supports CLI, API and manual deployment workflows, so it would be misleading to say that every Netlify redirect change always requires the same Git redeploy path.
RedirHub gives redirect operations their own workspace. Approved RedirHub Product Facts support bulk CSV import/export, a REST API, automatic HTTPS and independent domain/managed-link capacity. That can make the workflow easier to hand to SEO, marketing or IT without making those teams responsible for the application's routing files.
Neither model is inherently better. The ownership model is the product decision.
How to check your own setup#
- Separate redirects that belong to a Netlify application from domains or mappings that need to survive independently of that application.
- Count individually changed old URLs. If the migration has 10,000+ rules, test whether Netlify placeholders or wildcards simplify the set before assuming every URL needs an individual rule.
- Estimate Netlify's shared credit usage, including redirect requests, bandwidth, deploys and compute rather than treating its monthly plan price as a redirect-only price.
- For RedirHub, count connected domains and individually managed migration mappings separately.
- Decide who should own future changes: the application team in its deployment workflow, or a team operating redirects as shared infrastructure.
Redirects that need their own workspace?
Manage retired domains, cross-platform migrations and individually mapped URLs with their own workspace, CSV/API workflow and capacity model outside the application.
Start free trialFrequently asked questions
There is no separate redirect subscription. Redirects are part of Netlify's platform plans and their requests consume the shared usage-credit pool. Free is $0 with 300 credits/month; paid plans provide more credits and other platform features.
Netlify's documentation does not present 10,000 as a plan limit. It says that for 10,000 redirects or more, you should use wildcards or placeholders where possible and consider Edge Functions for more complex setups because serialized rule output can become too large.
In the standard documented static-routing workflow, rules in _redirects or netlify.toml are part of the site configuration that Netlify processes for deployment. Netlify also has other deployment and edge workflows, so it is safer to evaluate the exact implementation than to claim every possible redirect change always follows one deployment path.
Its current redirect-options documentation says 307 is unsupported and recommends 302 for temporary redirects. RedirHub supports 307 and 308 in addition to 301 and 302.
Yes. Netlify supports domain redirects for domains assigned to a site and automatically provisions and renews Let's Encrypt certificates for custom domains.
RedirHub is the stronger fit when redirects need to operate independently of a Netlify application: cross-platform website migrations, retired-domain portfolios, large source-to-destination mapping sets, or redirect ownership shared with SEO, marketing or IT.
TC is the Operations Manager at RedirHub, leading the company’s operational strategy and execution to ensure reliable, scalable redirect infrastructure. He oversees internal processes, cross-team coordination, and platform readiness while supporting customers through complex redirect implementations. With a strong understanding of large-scale domain operations and real-world edge cases, TC plays a key role in aligning product and customer success to deliver stable, high-performance redirection solutions.