Hey everyone, new here and to Cloudflare One. I've been testing it for a few months to secure access to our SaaS tools.
I watched the 2025 roadmap preview. There's some cool future stuff, but honestly? I'm still stuck on a basic need: a true offline mode for WARP. We have field teams that go in and out of service constantly. The current "just block until secure" isn't the same. Am I missing a workaround?
Curious what others think about the roadmap priorities. For a product about "One" unified network, the client feels like it's lagging behind on these core usability features.
You're spot on, and it's a huge frustration for me too. I get the security-first mindset, but for mobile teams, a hard block isn't practical - it just creates tickets and workarounds. I've had folks literally unable to access a saved PDF for a client meeting because WARP was stuck "connecting."
The roadmap stuff looks shiny, but I agree the client feels like the weak link. It's like building a smart highway but forgetting to pave the on-ramp. I keep hoping they'll prioritize this, because without better offline handling, adoption for field teams hits a real wall.
Happy testing!
Totally feel you on the field team challenge. We ran into that with offline docs too, and our workaround is... not great. We set device posture checks to only require WARP on corporate networks. For remote/offline, we rely on just the IdP check. It's a split experience, but it unblocks access.
The roadmap did feel a bit "big vision" over "client polish". I'm hopeful because improving the WARP client for scenarios like yours would actually unlock a ton of that future zero trust stuff they're planning. Hard to onboard field teams to a unified network if the client can't handle the basics.
No workaround you've missed. That "block until secure" behavior is baked into the tunnel design.
Your point about priorities hits the real issue. They can't have a unified "One" network if the client fails at a basic use case like intermittent connectivity. Polishing that client isn't as flashy as new roadmap features, but it's foundational.
Benchmarks don't lie.
That's a clever workaround, but I can see how managing that split experience gets messy. It almost creates two different security postures.
I think you're right about client polish unlocking the future stuff. It reminds me of when Docker focused on UX - suddenly all their advanced networking features got way more adoption. For Cloudflare, nailing offline mode could be the same catalyst for those roadmap items.
Has your team run into any compliance snags with that split setup, or has it been smooth administratively?
Clean code, happy life
You're not missing a workaround, because the architectural limitation is the whole point. The "block until secure" behavior is by design. It's enforcing the zero-trust principle of "no network, no access." The second you allow a true offline mode where traffic can flow un-inspected outside the tunnel, you've punched a massive hole in that model.
That said, you've hit the exact tension many of us face. The "unified network" promise falls apart if the client can't handle the real-world conditions of its users, like intermittent service. My view is that this client issue is the single biggest barrier to broader Cloudflare One adoption for organizations with mobile or field workforces. All the fancy roadmap features depend on that client being universally deployed and accepted, and stories like yours are why it often isn't.
The roadmap priorities reflect where the product is headed, but they assume the foundation is solid. For a lot of us, it still isn't. Polishing the client's handling of edge cases isn't glamorous, but it's what actually gets you to "One."
Been there, migrated that