Product offerings
Private networking for home labs and company networks, with additional services chosen separately when you need them.
Where we are now
The Alpha is testing client enrollment, policy-controlled encrypted peer connections, and a dedicated company control plane built on NetBird. A dedicated controller means a separate virtual instance, not dedicated physical hardware.
Tell us what you need to connect and where your users are located. We will discuss evaluation scope and hosting location before a deployment is agreed. Managed upgrades, support responsibilities and any hands-on network work need an explicit scope.
Planned offerings · Not yet available
Private access to a NAS, home servers and your own devices, with a straightforward service scope.
Settings export is not a controller backup, a promise to export every secret, or a substitute for backing up your files.
Private access for employees, services and sites, with optional operational services selected individually.
Option prices, backup schedules, retention and recovery commitments are not set. We will define them before offering these services.
Optional services
These are planned modules, not features included in every service. A relay, a backup and a standby controller solve different problems.
Small Business and above
A separately selected backup option for controller recovery. Schedule, retention, restore testing and recovery objectives still need to be defined.
Small Business and above
A separately selected option for handling a controller failure. Architecture and failover validation are still in development; this is not a live HA service or an SLA.
Separately scoped option
More relay locations for networks that need them. NetBird supports external relays; VPNnet version-specific selection and failover tests are still pending.
Separately scoped option
A recovery environment in another region or, where permitted, another provider. Restore procedures and recovery times must be agreed and tested before service is offered.
Underlying capability is not the same as a validated VPNnet service. See NetBird’s external relay documentation. Multiple relays do not by themselves make a controller highly available.
Enterprise · Custom quote
Vultr is our standard hosting platform. A requirement to run only on AWS or only on Azure is an Enterprise engagement with a custom quote and an agreed deployment scope.
A provider-only requirement applies to the controller, relays, backup storage and disaster recovery. We will not silently put a recovery copy in another cloud.
No provider-specific deployment, recovery time or availability guarantee is being offered on this page.
What the terms mean
They can work together, but none is a replacement for the others.
A retained copy can help recover from loss or unwanted changes. A useful backup also needs a tested restore process. Daily frequency and retention are not yet defined for the planned business option.
It aims to reduce interruption when a controller or related component fails. It is not a historical copy of your data. The VPNnet design and failover tests are still under investigation; active-active service is not being advertised as implemented.
It addresses a larger failure, such as losing a region or provider. The recovery location must respect your placement requirements. Recovery time and how much recent data could be lost have not been committed.
No. Permitted peers prefer direct encrypted paths. Relays forward encrypted traffic when a direct path is unavailable. Extra relay locations are a separate option, and relayed traffic uses hosting transfer.
A suitable customer-owned gateway can route configured internet traffic through your connection. Filtering needs separately configured firewall or DNS software. Enabling an exit route alone does not add filtering or HTTPS inspection. Read the gateway example.
Plan with us
Home lab or company network, start with the people, resources, locations and responsibilities. We will separate what the Alpha can test from what still needs to be built.