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 traffic splitting, and privacy-first analytics. Common use cases include replacing Firebase Dynamic Links fallback flows, preserving paths during domain migrations, and sending mobile users to the App Store or Google Play while desktop users land on the web. We would love feedback on three things: 1. Which use case resonates most for you: migrations, smart links, or traffic routing? 2. Is the positioning around edge redirect infrastructure clear, or does it still feel too technical? 3. What would you want to see before trusting a product like this with production traffic? Thanks for checking out UrlEdge. We will be here answering questions.