Physical security of these boxes is really interesting (e.g. as CF holds a lot of SSL certificates the profit of hacking into these boxes is likely a lot higher than looks at first glance)
When I think of Cloudflare workers and such, I think of the public internet. If you have a public web app and you want low latency all around the globe, a worker is a great option.<p>This is the opposite of that. Are they targeting "inhouse apps" that until now would be self hosted by the organization? Basically cloud apps where the cloud is in your own building? Do they have good firewalls and access control for that, for different businesses in the same building? Can a business in the future install their <i>own</i> one of these?<p>Or is this just about businesses having access to the full Cloudflare network, just a little bit faster?
> First and foremost, it eliminates the need to rely on the costly, rigid hardware solutions<p>Instead, you have to depend on "free" (wrapped up in subscription charges), rigid hardware solutions provided only by Cloudflare.<p>It's an interesting product, and furthers Cloudflare's dominance strategy. It provides real value and at a cost that is invisible.
I don't understand their statement about MPLS and security: <i>"a need for MPLS to make their network operate securely"</i><p>Isn't MPLS used for routing and building SDN fabric where you applied a bunch of QoS rules depending of the MPLS tags ?, which as nothing to do with security.