Cloudflare Flagship

Cloudflare unveiled Flagship, a new tool that lets app makers quietly turn features on and off without pushing out a whole new update. In plain English: companies can test changes on a few people first, roll things out slowly, and avoid the dreaded “we shipped it and everything broke” moment. It also works with OpenFeature, an open standard meant to make these tools easier to swap around later. Very tidy, very practical, very “please don’t wake up the on-call engineer at 3 a.m.”

But the real show was in the comments, where the launch instantly became a referendum on the entire Cloudflare-vs-everyone-else tech universe. One commenter casually tossed in a Vercel alternative, basically lighting the fuse for a mini “who copied whom?” side quest. Another came in hot with the biggest applause-and-groan combo of the thread: Cloudflare is winning, they said, except for its annoying account permissions setup, which apparently forces some teams into weird separate-account gymnastics that mess with company sign-ins. Ouch.

Then came the classic internet energy: one person saying you can basically build a version of this yourself “with a few lines of code,” while another asked the most relatable question of all — do these off-the-shelf tools secretly slow everything down? That anxiety landed hard, thanks to a horror story about slow app startups tied to a similar Firebase service. The funniest twist? In a thread about a polished new product, half the community sounded impressed, and the other half sounded like they were already drafting their own homemade replacement.