Managed Nebula vs Self-Hosted Nebula

Last updated:

Abstract dark amber and rose gradient

Managed Nebula and self-hosted Nebula run the same open-source Nebula, with the same protocol, certificates, and firewall. The difference is who runs everything around it: the certificate authority, each host’s config, the lighthouses, and enrollment.

Nebula is a fully open-source overlay networking tool that we originally built at Slack and continue to maintain at Defined Networking. It is released under the MIT license, and the Nebula docs cover everything you need to run a network on your own. Plenty of people do, and we want them to.

Managed Nebula is our cloud-hosted management layer on top of it. Every host runs DNClient, an instance of Nebula instrumented to pull its configuration from our API. We run the certificate authority, issue and rotate certificates, distribute configuration and firewall rules, and provide a managed lighthouse. It is free for up to 100 hosts.

At a glance

Managed NebulaSelf-hosted Nebula
Data planeOpen-source NebulaOpen-source Nebula
CAHeld by Defined NetworkingHeld by you, via nebula-cert
Cert rotationAutomatic, hosts and CAsManual, before the CA expires
Config & firewallRoles and tags, admin panelYAML file on every host
Revoking a hostBlock it in the admin panelPush a blocklist to every host
LighthousesManaged one included, or yoursYou run them
EnrollmentEnrollment codes, join keys, SSOCopy cert, key, config to host
ClientDNClient and Mobile Nebulanebula and Mobile Nebula
Admin interfaceAdmin panel, API, audit logsConfig files, your own tooling
SupportEmail; priority and Slack by planGitHub, community Slack
CostFree to 100 hosts, then $1/host/moFree; your servers and time

The certificate authority

Every Nebula network starts with a certificate authority (CA). Each host’s certificate encodes its name, overlay IP, and groups, and two hosts authenticate each other by checking that their certificates were signed by a CA they trust. Whoever holds the CA’s private key decides who is on the network.

When you run Nebula yourself, you create the CA with nebula-cert ca and sign each host with nebula-cert sign. The Nebula quick start calls the resulting ca.key the most sensitive file you will create. Since v1.7.0, nebula-cert can encrypt it with a passphrase, and because it is only needed when you sign a certificate, you can keep it offline the rest of the time. Custody is entirely yours: no one else can sign a certificate for your network, and no one else can recover the key if you lose it.

Managed Nebula creates several CAs for your account, and we hold their private keys. Signing happens when a host enrolls or its certificate is rotated, with no CA key on any of your machines. Securing the keys to your kingdom explains how we protect them. Either way, each host generates its own private key locally, and that key never has to leave the host.

If holding your own CA key is a hard requirement, self-hosting is the way to meet it.

Certificate rotation and expiry

Nebula certificates expire, and when a CA expires, every certificate it signed stops working with it.

By default, nebula-cert ca creates a CA that expires after one year, and host certificates are valid until one second before their CA expires unless you pass -duration. The Nebula docs suggest setting a calendar reminder to rotate before then. Following the CA rotation guide, you create a new CA, append it to the trust bundle on every host and reload Nebula, sign a new certificate for every host and copy it into place, and then remove the old CA from every host. The guide recommends starting early, possibly months ahead, and doing it with a config management tool like Ansible, Chef, or Puppet.

Managed Nebula rotates certificates automatically. DNClient picks up each new host certificate from our API, and we rotate the CAs periodically and send the new CA certificates to every host. Peers validate certificates against the CA, so a host’s new certificate doesn’t have to be sent anywhere else.

Config and firewall rules

A self-hosted network gives every host a YAML config file holding its PKI paths, lighthouse addresses, firewall rules, and any other settings, and you get that file onto the host and keep it current. Firewall rules reference the groups in each host’s certificate, so changing a host’s groups means signing it a new certificate. Firewall rules, the CA trust bundle, and many other settings can be reloaded without restarting Nebula, but getting the new file onto every host is up to you.

Revocation works the same way. Nebula’s pki.blocklist lists the fingerprints of certificates to stop trusting, and the docs note that it is not distributed via lighthouses: to block a host everywhere, you push the updated blocklist to every host.

In Managed Nebula, you assign each host a role and tags in the admin panel. Roles carry inbound firewall rules, tags group hosts and can carry config overrides, and the result is the same Nebula firewall and config, generated for each host. DNClient holds a long-poll connection open to our service, so changes are applied nearly instantly. Blocking a host makes every other host that can reach our service stop trusting its certificate within 60 seconds.

Lighthouses and relays

Lighthouses let hosts find each other, and relays carry traffic between hosts that can’t connect directly. Neither ever sees inside your tunnels.

If you run Nebula yourself, you run these too. A lighthouse needs an address that doesn’t change and UDP (port 4242 by default) open to the internet, and every other host lists it in its static_host_map. The Nebula docs note that a lighthouse needs very few resources, so the least expensive instance from a cloud provider will do. Any host can be a relay by setting am_relay. If every lighthouse is unreachable, hosts that already have tunnels keep using them, but they can’t look up a peer they aren’t already talking to unless it’s in their static_host_map.

Every new Managed Nebula network includes a managed lighthouse at no extra cost, and it acts as a relay by default. It runs as a separate deployment from our API, so an API outage doesn’t take peer discovery down with it. You can still run your own: enroll a lighthouse or dedicated relays on-premise or in your own cloud, alongside ours for redundancy or instead of it. Lighthouses and relays you run yourself are billable hosts, like any other host you enroll.

Enrolling hosts

Adding a host to a self-hosted network means signing a certificate for it and copying the CA certificate, the host certificate, its private key, and a config file onto the machine. To keep the private key from ever leaving the device, you can run nebula-cert keygen on it and sign only the public key, which means moving files in both directions. Nothing about the new host has to be sent to the lighthouse or other hosts.

In Managed Nebula, you create a host in the admin panel and enroll it with a single-use enrollment code, or create a join key that any number of machines can enroll with, suited to CI runners, autoscaling groups, and MDM rollouts. DNClient Desktop can also enroll through single sign-on with your identity provider. The host generates its key, receives its certificate and config, and joins the network with its role and tags already applied.

DNClient and the nebula binary

On a self-hosted network, each host runs the nebula binary from the GitHub releases, a distribution package, or the official Docker image, on Linux, macOS, Windows, FreeBSD, OpenBSD, and NetBSD. You choose when to upgrade.

Managed Nebula hosts run DNClient. DNClient Desktop is a Mac and Windows app with a menu bar icon and SSO enrollment. DNClient Server is a CLI and service for servers, installed from packages, as a standalone binary, or as a Docker image. Both run Nebula inside, so the tunnels, encryption, and firewall are identical to the open-source build.

On phones and tablets the client is the same either way. Mobile Nebula for iOS and Android connects to both. The app calls each network a site: you configure a self-hosted site by hand, and a Managed Nebula site is set up for you when you enroll the device with a code, link, or QR code.

Admin panel, API, and audit logs

Open-source Nebula is a binary and a config file, with no admin interface. Inventory, change history, and access control for whoever edits the configs come from your own tooling, usually config management and version control. Nebula does expose stats for Prometheus or Graphite and an optional debug SSH server on each host.

Managed Nebula has a web admin panel with unlimited admins and SSO through your identity provider on every plan. Every change is recorded in audit logs you can filter and export, and you can automate the network through the API with scoped API keys. For infrastructure as code, the Defined Networking Terraform provider manages networks, roles, tags, and routes, and also works with OpenTofu.

When Defined Networking is down

Our API is not in the path of your traffic. Once a host has its certificate and configuration, it doesn’t need to reach us to operate. If our API becomes unreachable, hosts keep their tunnels, traffic flows, and firewall rules continue to be enforced. The managed lighthouse runs separately, so hosts keep finding each other. Until the API returns, you can’t push config changes, enroll hosts, or block a host. Read more in our architecture overview.

If you want no dependency on us at all, even for discovery, run your own lighthouses and relays and turn off the managed lighthouse. As our pricing page notes, that keeps your network operating even in the unlikely event that Managed Nebula is unavailable.

Self-hosted Nebula has no outside dependency, but keeping it available is up to you: running the lighthouses, backing up the CA key, and distributing config.

Support

For self-hosted Nebula, help comes from the Nebula docs, GitHub issues, and the NebulaOSS Slack community linked from the project’s README.

Managed Nebula customers can reach our support team by email or through the admin panel. Pro adds priority support and guaranteed uptime, and Enterprise adds a dedicated Slack support channel and help with network design and setup. Support comes from Defined Networking, which also maintains Nebula.

Pricing

Managed Nebula offers simple per-host pricing:

  • Free: Up to 100 hosts, 2 routes, SSO, and a simple management UI. No credit card required.
  • Pro: $1/host/month with unlimited hosts, up to 100 routes, priority support, and guaranteed uptime
  • Enterprise: Custom pricing with a dedicated Slack support channel and network design assistance

See our pricing page for full details, or contact sales for Enterprise.

Self-hosted Nebula is free software. The cost is the servers for your lighthouses and relays, the tooling to sign certificates and distribute config, and the engineering time to rotate certificates and keep it all running. For a few hosts that cost is small. For a fleet, CA rotation alone means touching every host, by default once a year.

Which is right for you?

Choose Managed Nebula if you want:

  • Certificates issued and rotated for you, with no CA expiry to track
  • Firewall rules and config managed through roles and tags instead of per-host files
  • Hosts that enroll with a code, a join key, or SSO
  • A managed lighthouse on day one, with the option to run your own lighthouses and relays
  • An admin panel, audit logs, an API, and a Terraform provider
  • Support from the company that maintains Nebula, with an uptime guarantee on Pro
  • To start free and stay free up to 100 hosts

Choose self-hosted Nebula if you want:

  • To hold your own CA private key, possibly offline
  • No external service in the picture at all, including for enrollment and config
  • To fit Nebula into config management you already run, like Ansible, Chef, or Puppet
  • Full control over every config option on every host
  • A network of a handful of hosts where operating it yourself is part of the fun

Either way, you are running Nebula. Managed Nebula is built on the same open-source project, and our architecture overview explains how you could export your host configs, create your own CA, and run Nebula directly if you ever wanted to leave.

Self-hosted Nebula details verified against Nebula v1.12.0 and the Nebula documentation, November 2026.


Frequently asked questions

Is Managed Nebula a fork of Nebula?

No. Managed Nebula runs the same open-source Nebula. Every host runs DNClient, which wraps Nebula with enrollment, automatic certificate updates, and centralized config, but the networking, encryption, and firewall are Nebula's. Defined Networking maintains the open-source Nebula project as well.

Can I run Nebula without Defined Networking?

Yes. Nebula is open source under the MIT license. You create a certificate authority with nebula-cert, sign a certificate for each host, write each host's config file, and run your own lighthouses. Nothing in the open-source project depends on Defined Networking's service.

Who holds the CA private key?

When you self-host, you do: the ca.key file signs every host certificate, and the Nebula docs call it the most sensitive file you will create. With Managed Nebula, Defined Networking creates several CAs for your account, rotates them, and keeps the private keys secure. In both cases each host generates its own private key, which never has to leave the host.

What happens to a Managed Nebula network if Defined Networking is down?

Hosts keep their certificates, tunnels stay up, traffic flows, and firewall rules are still enforced. The managed lighthouse runs separately from the API, so peer discovery keeps working too. What you lose until the service returns is the ability to push config changes and enroll new hosts.

Does Mobile Nebula work with self-hosted Nebula?

Yes. Mobile Nebula for iOS and Android connects to both. For a self-hosted network you add a site and supply its certificate and config yourself. For Managed Nebula you enroll the device with a code, link, or QR code and it arrives fully configured.


Related comparisons

Encryption that works

Fast, secure overlay networking with unlimited scalability. Up to 100 hosts free, no credit card required.

Get started