Firezone

Firezone's getting a new look! firezone.dev/blog/new-ui-la…

A new look for Firezone is coming soon: firezone.dev/blog/new-ui-la…

We plan to roll out the final phase of our GCP -> Azure migration today. We don't expect any noticeable downtime, but make sure to check firezone.statuspage.io if you experience issues!

January 2026 Devlog - Multi-region infrastructure, snappier admin portal, and more: firezone.dev/blog/devlog/20…

October 2025 Devlog October delivered substantial improvements to Gateway observability, Linux networking stack refinements, and new deployment mechanisms. Read the full post: firezone.dev/blog/devlog/20…

We've got a fix in the works that should fully resolve the issue going forward: github.com/firezone/firez… Read more about PNA here: wicg.github.io/private-networ…

In Firezone's case, it means you might see errors related to CORS in your browser console for requests to remote hosts that match DNS resources you've configured in your account.

Google's shipping a new feature in Chrome that breaks many VPN and DNS security products - Firezone included. It's called Private Network Access, and it blocks requests to "private" networks if they originated from a "public" network.

September 2025 Devlog September was all about boosting Firezone’s reliability, performance, and admin tools — with more resilient connections, better client version management, and an optimized networking stack for real-world use.

September 2024 update We're excited to announce some major new features we've been cooking over the last few months that should make Firezone even more flexible and easier to use: - Full-route tunneling ("Internet" Resources) - REST API (beta) - Improved wildcard matching for DNS Resources Read more: firezone.dev/blog/sep-2024-…

It's been an incredible journey, and we're just getting started!

🎉 Firezone is Now SOC 2 Compliant 🎉 We are excited to share that Firezone is now SOC 2 compliant! This significant underscores Firezone's commitment to keeping customer data safe and sound. Huge thanks to our amazing team for all their hard work, and to our awesome customers and partners for your trust and support. We look forward to continue delivering the fastest, easiest way to scale zero-trust across your organization. Request a copy of the report here: trust.firezone.dev. #SOC2 #CyberSecurity #ZeroTrust #DataProtection #Firezone

Fan of #rustlang? Read about how our sans-IO data plane architecture reliably powers Firezone's connectivity stack across all kinds of devices: firezone.dev/blog/sans-io

Version 1.1 clients have shipped -- upgrade today. - DNS Resources are *much* more reliable on unreliable networks - New feature: 🪄AutoNAT🪄Connect to IPv6 DNS Resources from IPv4-only networks, no configuration necessary. It just works. firezone.dev/changelog

🔥June 2024 update:🔥 - Conditional access policies - Directory sync support for JumpCloud - Reliability improvements for DNS Resources on certain networks Read more: firezone.dev/blog/jun-2024-…

How we got our Windows and Linux clients from zero to market so quickly (hint: @TauriApps!): firezone.dev/blog/using-tau…

🔥May '24 update 🔥 - New feature: Port and protocol traffic restrictions - Blog: How DNS works in Firezone - Improved connection time and reliability Read more: firezone.dev/blog/may-2024-…

We put together a few guides to show how you can solve the most common secure access scenarios using the new Firezone, like scaling access into a VPC, blocking malware across your workforce, and managing access to a pubic SaaS app: firezone.dev/kb/use-cases