I'd suggest you scrap your "fancy" website and replace it with two paragraphs of text that explain what you are trying to sell and how it works.<p>The "vague bullshit in between cute animations" approach really doesn't work at all for this type of product.
Their twitter feed has a diagram describing the process on AWS: <a href="https://twitter.com/datapath_io/status/560027255188250625/photo/1" rel="nofollow">https://twitter.com/datapath_io/status/560027255188250625/ph...</a><p>EDIT another: <a href="https://twitter.com/datapath_io/status/559741202342625280/photo/1" rel="nofollow">https://twitter.com/datapath_io/status/559741202342625280/ph...</a>
Doesn't every CDN already accomplish the same functionality with multiple origins and failover detection, while accelerating static content by caching it at the edge? Given how cost competitive CDNs already are, I don't see how they can charge a low enough cost in comparison to be compelling, while still incurring bandwidth costs and at least some network infrastructure which make it almost as expensive to run, minus some caching nodes. And if for whatever reason, there does happen to be some use case for anycasting the IP that's advantageous, any CDN could add this feature overnight while having a much more established footprint and infrastructure in place.
> If your application goes down, all you want is to get it back up. What if your cloud provider is down? Use DATAPATH.IO to route your users to a healthy location while keeping your IP addresses.<p>But... what happens if datapath.io goes down?
I assume this is BGP routing as a service (which sounds cool).<p>But, would this not break the internet if everyone used it? routing individual IPs (rather than large blocks) sounds like it would end in chaos?
> What if your cloud provider is down? Use DATAPATH.IO to route your users to a healthy location while keeping your IP addresses.<p>Call me crazy, but I'm not sure I really <i>care</i> about keeping my IPs. Route 53 seems as close to bulletproof as we're going to find with DNS, and it's got cloud-independent failover routing built in. Point the primary record at your nice little EC2 server, and have the secondary record pointing as Azure or Google Cloud or your mom's laptop, whatever, and it'll do what Datapath is doing without futzing with your routing. ...right?