Commit Graph
4 Commits
Author SHA1 Message Date
Jack Carter 7d1ca1d635 Mention the Enterprise Commercial License wherever a Cloud plan gates a feature (#1023)
* docs: mention the Enterprise Commercial License wherever a Cloud plan gates a feature

Cloud-plan and cloud-only notes now also name the self-hosted Enterprise
Commercial License for IdP sync, EDR/MDM, peer approval and MFA. The Zero
Trust guide, Plans and billing and Self-hosted vs Cloud gain self-hosted
equivalents. SSO notes state that OIDC IdPs work in both self-hosted
editions. The license page's feature table adds peer approval, audit event
streaming and notifications.

* docs: drop the MFA license claim; self-hosted MFA covers local users only

* docs: state that an Enterprise proof of concept includes every licensed feature
2026-10-06 15:53:32 +02:00
Jack Carter e1e836e00e docs: describe what the Enterprise server shares with the license service (#978) 2026-09-16 16:42:00 +02:00
Bethuel Mmbaga f51e8ea987 Simplify enterprise setup steps (#877) 2026-07-23 12:41:26 +03:00
Jack Carter e4b4eb737c docs: add Enterprise Commercial License overview page (#869)
* docs: add Enterprise Commercial License overview page

Add a public, shareable overview of the NetBird Enterprise Commercial
License for teams evaluating self-hosted NetBird. Answers the questions
prospects ask most: in-place migration from the open source Community
Edition, zero-downtime control-plane upgrades via active-active HA,
control-plane behavior at scale, single-tenant boundaries and the
options for serving multiple customers, and how evaluation works.

Clarifies that the Cloud "Business plan" and the self-hosted commercial
license are different products, and lists what the license unlocks
(HA, SCIM, EDR/MDM integrations, traffic-flow logging, standard support).

Served at /selfhosted/enterprise and linked from the Self-Host sidebar.

* docs: qualify connection continuity by deployment topology

The single-server upgrade answer claimed all established connections
survive a restart. That holds only when Relay runs externally. In the
default combined deployment, netbird-server bundles Management, Signal,
and Relay, so recreating it restarts Relay and active relayed sessions
reconnect. Clarify that direct peer-to-peer connections continue either
way, while relayed-session continuity depends on whether Relay is
external or restarted with the combined server.

* docs: describe the commercial PoC as assisted, with 30-day default

"Managed proof of concept" overstated the offer. Per the EULA the
customer installs and runs the stack, with NetBird providing the license
and guidance, and a commercial PoC runs 30 days by default. Reword to
"assisted proof of concept" and state the default duration.
2026-07-22 16:50:06 +02:00