All activity
UrlEdge lets you run redirects, smart links, URL masking, and A/B or device-based routing at the edge. Use one branded URL for migrations, app-store fallbacks, and campaign traffic without touching server config. The free-forever plan is generous enough for real projects: 5 domains, 15 rules, and 100,000 monthly requests before you need a paid tier.
UrlEdgeFree edge redirects, smart links, and device-based routing
Evan Stackstarted a discussion
What breaks most often in your redirect or smart-link setup?
We're preparing UrlEdge for launch and would love to learn how teams are handling redirects today. If you've dealt with domain migrations, smart links, app-store fallbacks, or campaign routing, what tends to break first? - origin or server config drift - analytics attribution loss - device or geo fallbacks - bulk rule changes and QA - SEO risk during migrations We're especially interested in...
Evan Stackleft a comment
Hey Product Hunt! We built UrlEdge after seeing redirects handled across too many layers: DNS providers, app middleware, Nginx rules, short-link tools, and ad hoc scripts. That makes migrations risky, smart links brittle, and campaign routing harder to debug. UrlEdge gives teams one edge-based layer for 301/302 redirects, smart links, path forwarding, device and geo routing, URL masking, A/B...
UrlEdgeFree edge redirects, smart links, and device-based routing