Nebula
github.com · Egress and tunnels · 1 record · JSON
Nebula Egress and tunnels
fails: egressanonymousno cardI
| Free tier | 'Nebula is a scalable overlay networking tool with a focus on performance, simplicity and security. It lets you seamlessly connect computers anywhere in the network.' Self-hosted; no quota. unit unlimited; metered on none |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No allowance: there is no vendor and no hosted service.; ingress: none free_allowance: none published |
| Identity | anonymous self-hosted; membership is a signed certificate from the operator's CA |
| Binding | none Nothing meters bytes and nothing publishes a port, so no constraint fires at 1 TiB/month because the traffic cannot leave the overlay. |
| Interface | cli config files plus a certificate authority the operator runs |
| Tooling | nebula and nebula-cert binaries |
| Composes with | a private overlay that composes with a public ingress and adds none |
| Reliability | self-operated; certificate issuance and lighthouse uptime are local work |
| Notes | Included because the supplied list names it and because a reader will confuse it with a WireGuard tool. It is the one provider here where I could not read a protocol statement, so wg_path stays unknown rather than being filled from memory. |
| Evidence rung | inferred The overlay claim is quoted; the 'no ingress' conclusion is inferred from the description, because a feature that does not exist has no page saying so. Reading the lighthouse documentation would raise this to documented. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | github.com/slackhq/nebula | 'Nebula is a scalable overlay networking tool'; it 'lets you seamlessly connect computers anywhere in the network' and combines 'encryption, security groups, certificates, and tunneling' |
More fields (7)
{
"wg_path": "unknown",
"wg_detail": "The repository describes 'encryption, security groups, certificates, and tunneling' without naming WireGuard; no protocol page was read today, so whether the transport can carry a WireGuard datagram is open.",
"ingress": "none",
"volume_tib_month": null,
"volume_stated": "No allowance: there is no vendor and no hosted service.",
"bytes_transit": "overlay-only",
"transit_note": "peers relay through lighthouses only to find each other; payload goes peer to peer"
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable