HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
slackhq
nebula
Go2019–2026
slackhq / nebula

nebula

A scalable overlay networking tool with a focus on performance, simplicity and security

64Distinct people
74Mentions
1Explicit recommenders
18.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A scalable overlay networking tool with a focus on performance, simplicity and security

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Wireguard isn't so good for mesh networks because every new node requires reconfiguring all the others. Even with management utilities this is a pain, so instead I recommend…

alephu5 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year74 dated mentions

Observed mentions: 2019-11-19 20:01:13 UTC to 2026-08-27 15:41:17 UTC.

0510152019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 17 mentions; 5 submissions, 12 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC312
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC808
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC11110
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC17512
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC13112
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC11011
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC716
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC404

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
What is Nebula? Nebula is a scalable overlay networking tool with a focus on performance, simplicity and security. It lets you seamlessly connect computers anywhere in the world. Nebula is portable, and runs on Linux, OSX, Windows, iOS, and Android. It can be used to connect a small number of computers, but is also able to connect tens of thousands of computers. Nebula incorporates a number of existing concepts like encryption, security groups, certificates, and tunneling. What makes Nebula different to existing offerings is that it brings all of these ideas together, resulting in a sum that is greater than its individual parts. Further documentation can be found here. You can read more about Nebula here. You can also join the NebulaOSS Slack group here. Supported Platforms Desktop and Server Check the releases page for downloads or see the Distribution Packages section. Linux - 64 and 32 bit, arm, and others Windows MacOS Freebsd Distribution Packages Arch Linux sudo pacman -S nebula Fedora Linux sudo dnf install nebula Debian Linux sudo apt install nebula Alpine Linux sudo apk add nebula macOS Homebrew brew install nebula Docker docker pull nebulaoss/nebula Mobile (source code) iOS Android Technical Overview Nebula is a mutually authenticated peer-to-peer software-defined network based on the Noise Protocol Framework. Nebula uses certificates to assert a node's IP address, name, and membership within user-defined groups. Nebula's user-defined groups allow for provider agnostic traffic filtering between nodes. Discovery nodes (aka lighthouses) allow individual peers to find each other and optionally use UDP hole punching to establish connections from behind most firewalls or NATs. Users can move data between nodes in any number of cloud service providers, datacenters, and endpoints, without needing to maintain a particular addressing scheme. Nebula uses Elliptic-curve Diffie-Hellman (ECDH) key exchange and AES-256-GCM in its default configuration. Nebula was created to provide a mechanism for groups of hosts to communicate securely, even across the internet, while enabling expressive firewall definitions similar in style to cloud security groups. Getting started (quickly) Don't want to manage your own PKI and lighthouses? Managed Nebula from Defined Networking handles all of this for you. To set up a Nebula network, you'll need: 1. The Nebula binaries or Distribution Packages for your specific platform. Specifically you'll need nebula-cert and the specific nebula binary for each platform you use. 2. (Optional, but you really should..) At least one discovery node with a routable IP address, which we call a lighthouse. Nebula lighthouses allow nodes to find each other, anywhere in the world. A lighthouse is the only node in a Nebula network whose IP should not change. Running a lighthouse requires very few compute resources, and you can easily use the least expensive option from a cloud hosting provider. If you're not sure which provider to use, a number of us have used $6/mo DigitalOcean droplets as lighthouses. Once you have launched an instance, ensure that Nebula udp traffic (default port udp/4242) can reach it over the internet. 3. A Nebula certificate authority, which will be the root of trust for a particular Nebula network. ./nebula-cert ca -name "Myorganization, Inc" This will create files named ca.key and ca.cert in the current directory. The ca.key file is the most sensitive file you'll create, because it is the key used to sign the certificates for individual nebula nodes/hosts. Please store this file somewhere safe, preferably with strong encryption. Be aware! By default, certificate authorities have a 1-year lifetime before expiration. See this guide for details on rotating a CA. 4. Nebula host keys and certificates generated from that certificate authority This assumes you have four nodes, named lighthouse1, laptop, server1, host3. You can name the nodes any way you'd like, including FQDN. You'll also need to choose IP addresses and the associated subnet. In this example, we are creating a nebula network that will use 192.168.100.x/24 as its network range. This example also demonstrates nebula groups, which can later be used to define traffic rules in a nebula network. ./nebula-cert sign -name "lighthouse1" -ip "192.168.100.1/24" ./nebula-cert sign -name "laptop" -ip "192.168.100.2/24" -groups "laptop,home,ssh" ./nebula-cert sign -name "server1" -ip "192.168.100.9/24" -groups "servers" ./nebula-cert sign -name "host3" -ip "192.168.100.10/24" By default, host certificates will expire 1 second before the CA expires. Use the -duration flag to specify a shorter lifetime. 5. Configuration files for each host Download a copy of the nebula example configuration. On the lighthouse node, you'll need to ensure am_lighthouse: true is set. On the individual hosts, ensure the lighthouse is defined properly in the static_host_map section, and is added to the lighthouse hosts section. 6. Copy nebula credentials, configuration, and binaries to each host For each host, copy the nebula binary to the host, along with config.yml from step 5, and the files ca.crt, {host}.crt, and {host}.key from step 4. DO NOT COPY ca.key TO INDIVIDUAL NODES. 7. Run nebula on each host ./nebula -config /path/to/config.yml For more detailed instructions, find the full documentation here. Building Nebula from source Make sure you have go installed and clone this repo. Change to the nebula directory. To build nebula for all platforms: make all To build nebula for a specific platform (ex, Windows): make bin-windows See the Makefile for more details on build targets Curve P256 and FIPS 140-3 mode The default curve used for cryptographic handshakes and signatures is Curve25519. This is the recommended setting for most users. If your deployment has certain compliance requirements, you have the option of creating your CA using nebula-cert ca -curve P256 to use NIST Curve P256. The CA will then s
Read the full README on GitHub

What Hacker News says

17 sources
nebula[0] may be interesting; you can allow list connectivity for specific groups, all burned into the cert used to join the network. It uses some NAT hole punching orchestration to accomplish connectivity between hosts without opening ports. The main painful thing I've found has been cert management. PKI, as usual, is not a solved problem. I've managed to do some fun stuff using salt + nebula on the hobby side. [0] https://github.com/slackhq/nebula
In Golink: A private shortlink service for tailnets
>I've been meaning to look into this with wireguard, but I'm having trouble searching for/finding how to do this. Is "bastion host" what I'd want? Also is there a way to ensure the VPS cannot access the network as well, and just tunnels it essentially? First, yes a search phrase like that should get you the right terms, though there isn't anything inherently special about it. If multiple systems are connected to one system with wireguard giving them all access to a given subnet is straight forward. As far as the VPS, it can indeed access that subnet too, since it's acting as part of the subnet, but you can use normal firewall rules on the far side internally to control what can talk to what and how. And in this kind of specific instance the WG is more about controller public facing surface area, the Bitwarden/Vaultwarden traffic in flight
Read the rest
is itself encrypted. Second though, having said all that I think if you worried about the VPS bit (or even if not) you should take a look at the Nebula SDN [0, 1] instead. It's built on the Noise encryption framework as well. There, the fixed IP node (the "Lighthouse") primarily acts to let other nodes know their mutual addresses, and they then attempt to form a direct link with no bouncing through a bastion, it's a real mesh. This generally works even if both are NAT'd, and if not it's transparent fallback and still encrypted between them. Depending on distance between nodes this can be a lot lower latency as well. With Nebula you establish an internal CA (super easy built-in tool for it) and that doesn't (and absolutely shouldn't) live on the lighthouse. I'm fortunate enough to have fixed IPs available to me at home and office and have tended to use WG a lot just because it's had more advanced support and performance in constrained environments for me (kernel support in Linux and now BSDs). Nebula has been super slick though and I've been using it more and more. It makes all this really easy. Anyway, hope this helps a bit. It's really exciting to me how much open source networking power is now available to everyone. It's a bit of a counter decentralization force IMO to the last few decades push towards central service providers. ---- 0: https://github.com/slackhq/nebula 1: https://arstechnica.com/gadgets/2019/12/how-to-set-up-your-o... (note 3 years old, there are now Android/iOS clients as well and things are further refined)
In Passwordless Authentication – Access Your Bitwarden Web Vault Without a Password
pyajamas·Jun 13, 2022Submission

Show HN: A public Lighthouse service for Slack's nebula VPN

Slack's nebula VPN is a great networking tool with a focus on performance, simplicity and security based on the Noise Protocol Framework. However, for many people it is difficult to set up their own VPN, as a Lighthouse server is always required. That is why I started the public Nebula VPN Lighthouse Servers project [2]. This project aims to provide public Lighthouse servers for everyone. It consists of a python based snap app [3] that acts as a web server and allows anyone to use the public servers as a lighthouse for their own VPN. Snap's confinement is used to secure the server and users of the service should make sure to lock the Lighthouse out of the network [4]. If any of you have the ability to run a public Nebula VPN Lighthouse server, I would appreciate it if you would add your server to the server list [5]. As a nebula VPN user,
Read the rest
1 points · Open discussion
This is very nice and looks like a useful tool. It's also very much not a "Tailscale Alternative" – it explicitly describes itself as not being "a tool for creating mesh networks", which is the exact thing that Tailscale is all about. Nebula (https://github.com/slackhq/nebula) is much closer to actually being a fully open-source and self-hostable Tailscale alternative as I understand it, though I've never used it myself.
In FireZone – Open-source VPN server and firewall
Thanks :) We are using Nebula[1] to provide an encrypted private meshed network per project, so each project have it's own network range. We have automated that with a rest api and have published it as an open source project[2] It's really cool because you have out of the box a private network across all cloud providers and also works for on-premise deployments [1] https://github.com/slackhq/nebula [2] https://github.com/elestio/nebula-rest-api
In Show HN: Elestio – Managed platform for over 150 open-source software stacks

Showing the 15 most recent of 17 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.