|
| 1 | +--- |
| 2 | +title: "Defguard 2.0 Release Alpha 2 is now available" |
| 3 | +seoTitle: "Defguard 2.0 Release Alpha 2: Feature-Complete Preview for Early Testing" |
| 4 | +description: "Defguard 2.0 Alpha 2 is now nearly feature-complete. This release introduces faster setup, high-availability improvements, firewall management updates, and static IP assignment for users and devices." |
| 5 | +publishDate: 2026-03-10 |
| 6 | +author: "Robert Olejnik" |
| 7 | +image: "/images/blog/alpha2.0-2/Alpha%202.png" |
| 8 | +tags: ["defguard", "2.0", "alpha", "release", "wireguard", "enterprise vpn", "high availability", "firewall"] |
| 9 | +draft: false |
| 10 | +--- |
| 11 | + |
| 12 | + |
| 13 | + |
| 14 | +Due to high anticipation from our customers and users, we are excited to release the second alpha of version 2.0, which is now nearly feature-complete. |
| 15 | + |
| 16 | +While we still do not recommend it for production setups, we encourage teams running Proof of Concepts or early testing to deploy 2.0 Alpha 2 instead of the 1.6.x series. |
| 17 | + |
| 18 | +If you missed Alpha 1, read the [technical overview of Defguard 2.0](https://defguard.net/blog/defguard-20-alpha-technical-overview/#why-a-major-upgrade-1), where we explain why these architecture and UX changes were introduced. |
| 19 | + |
| 20 | +## What's changed in Alpha 2 (vs Alpha 1) |
| 21 | + |
| 22 | +### New quick setup wizard and VM images |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | +If you deploy 2.0 using [Docker Compose](https://docs.defguard.net/2.0/deployment-strategies/previewing-defguard-v2.0-alpha) or the new virtual image: |
| 27 | + |
| 28 | +- All components are automatically deployed (Core, Edge, and Gateway) |
| 29 | +- All components are automatically provisioned |
| 30 | +- The remaining steps are basic general settings and first VPN location setup in a guided wizard |
| 31 | + |
| 32 | +We designed this path to make evaluation and onboarding significantly easier. |
| 33 | + |
| 34 | +The main configuration wizard (first introduced in Alpha 1 and updated in this release) remains available and should be used for production-style deployment planning, where each component is launched separately. |
| 35 | + |
| 36 | +### High Availability: multiple Gateways and Edge components |
| 37 | + |
| 38 | +We added gateway setup: |
| 39 | + |
| 40 | + |
| 41 | + |
| 42 | +And gateway management: |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | +We also updated the testing Docker Compose to deploy multiple gateways that can be load-balanced with [Envoy](https://www.envoyproxy.io/), so you can validate HA behavior in test environments. |
| 47 | + |
| 48 | +### Firewall management |
| 49 | + |
| 50 | +New firewall management is now available for testing: |
| 51 | + |
| 52 | + |
| 53 | + |
| 54 | +Firewall management builds on 1.x concepts and expands them for 2.0. For deeper context, see [firewall improvements in the Alpha 1 technical overview](https://defguard.net/blog/defguard-20-alpha-technical-overview/#firewall-rules-changes-1). |
| 55 | + |
| 56 | +### Static IP assignment for users and devices |
| 57 | + |
| 58 | +A long-awaited feature is finally here. You can now assign IP addresses to networks and user devices from user and device context menus. |
| 59 | + |
| 60 | + |
| 61 | + |
| 62 | + |
| 63 | + |
| 64 | +### Easier Edge and Gateway deployment |
| 65 | + |
| 66 | +When adding a new Gateway or Edge component, the wizard now includes clearer deployment guidance: |
| 67 | + |
| 68 | + |
| 69 | + |
| 70 | +### Summary and release plan |
| 71 | + |
| 72 | +We included numerous bug fixes and smaller improvements in this alpha. There is still work ahead, but 2.0 Alpha 2 is ready for serious testing and feedback. |
| 73 | + |
| 74 | +Please share your feedback by [opening a GitHub discussion](https://github.com/defguard/defguard/discussions) or [submitting issues](https://github.com/defguard/defguard/issues) for bugs and missing features. |
| 75 | + |
| 76 | +Our plan is to release the first Beta in the coming weeks, including an automated wizard-based migration from 1.x. That will allow all customers to test migration flows in staging before final 2.0 rollout. |
| 77 | + |
0 commit comments