Firezone

Introducing sanstun: A sans-IO, parallel-friendly, userspace WireGuard implementation in Rust firezone.dev/blog/introducin…

v2 of the @firezonehq bare metal testbed is nearing completion. We already have both cloud and CI testbeds for performance, so why have another? Simple - bare metal exposes the hardware metrics necessary to optimize Firezone further. The new testbed consists of: - One Intel server and one AMD server with speedy Mellanox network cards - Two Macs directly connected via Thunderbolt Ethernet - Two Chromebooks - Two laptops - Various Apple and Android phones The goal for this testbed is to set some new throughput records for VPNs on commodity hardware. Stay tuned!

Employee terminated? Role changed? See how Firezone handles these events within seconds, not hours or days. firezone.dev/blog/building-r…

Learn how Beaver Excavating uses Firezone to connect construction sites to central HQ... over Starlink! youtube.com/watch?v=o7Z0dqtH…

Your network is only as secure as the devices connecting to it. So let's raise the bar. Today we're shipping Device Trust in Firezone: Lock down access to only the devices your organization trusts. Available now on every plan! See how to set it up: firezone.dev/kb/device-trust

We're pleased to announce that Audit Logs are now GA for all plan levels. These are already enabled on your Firezone account and can be found by navigating to the "Logs" sidebar item in your admin portal. Audit Logs come in four flavors: 1. Change Logs These log record-by-record updates of all changes to your account: who created/updated/deleted what when. All data is preserved: updates carry the diff of what changed (old vs new) and deletes show the data that was removed. These are built from the database write-ahead log, so they naturally preserve strict ordering and reflect the exact timestamp at which each change was committed. 2. Session Logs Every time a client or gateway connects to our control plane, and every time an admin signs in, we log which user and device it was and from where. These are session logs. 3. API Request Logs Every REST API request made in your account - the user agent, path, HTTP method, body size, and location from where the request was made. 3. Flow Logs Each time a user's device talks to a Resource, its Firezone client requests an authorization to do so. This policy authorization stamps the user, device, and resource that was accessed, but until now it omitted any kind of network-level information about the underlying traffic that was transmitted. Flow logs fix that. All TCP and UDP network flows that happened for each Resource in your account are tracked and reported - inner and outer tuples, packet and byte counts, IP addresses involved. Flow logs are tricky to get right: a) they're the only one in this list that are captured on endpoints we don't own or maintain b) they're tallied in the packet hot path so processing budget is tight c) they need to be buffered to disk to preserve accounting across crashes or sudden restarts d) malicious devices can tamper with data We solved all of the above with a two-sided reporting system - each side of the connection reports (hopefully) matching logs. We pair these up for you in the admin portal so you can quickly identify when the sides don't agree. All four of the log types above are also available today to sink into the following SIEMs and log aggregators: - Splunk - Elastic - Microsoft Sentinel - IBM QRadar - NewRelic - Datadog - Amazon S3 - Universal HTTP ------------ Check our docs for more on all of the above: - Audit Logs: firezone.dev/kb/audit-logs - Log Sinks: firezone.dev/kb/log-sinks

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

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/202…

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/202…