Defined Networking

Name: Defined Networking
Brand: Defined Networking

AI Native

From the creators of Nebula, the overlay networking tool, we're building secure mesh VPN software for every organization

Est 2020|Valuation $65M|Raised $18.9M|1 Ref Customers

LinkedIn 254|Web traffic 8K|FTEs 10|HQ Santa Monica, California, US

MarketsEnterprise Networking

Published Oct 15, 2026

01Common complaints

- If you need a “complete enterprise ZTNA platform” - Consider alternatives if you need device posture, broad compliance attestations, packaged security workflows, and extensive third-party integrations. - If you cannot (or will not) run networking infrastructure components - Defined’s pricing FAQ emphasizes you should run your own lighthouses and relays to control uptime; if that’s incompatible with your ops model, choose a solution that offers fully managed relays/coordination. - If you need abundant third-party validation - If procurement requires many verified third-party reviews (G2/TrustRadius/Gartner Peer Insights) and formal analyst coverage, Defined may be harder to justify today due to limited accessible review footprint. - If you need a clear public SLA / status reporting - “Guaranteed uptime” is mentioned in Pro pricing, but without an easily located public SLA/status page in the sources accessed, risk-averse buyers may prefer vendors with explicit SLA documents and public incident history. - If you need frequently changing network addressing - The docs state the overlay CIDR can’t be changed after initial setup; if your environment is still evolving and you expect to re-address often, this constraint can be painful. - Compliance transparency gap - No public SOC 2 / ISO 27001 information was found; this is a practical limitation for enterprise procurement. - Operational responsibility remains - You must run lighthouses and relays; vendor frames this as a benefit (you control uptime), but it’s also a burden. - “Guaranteed uptime” ambiguity - Pro tier includes “Guaranteed uptime,” but no public SLA document was located in the research sources, limiting verifiability. - Configuration constraints - Docs indicate the overlay CIDR cannot be changed after initial setup, which can be a meaningful limitation for evolving environments. - Review footprint is thin - Limited discoverability of product-specific reviews on major B2B review platforms increases buyer diligence burden (POC required).

02Why they buy

- “Customer-run data plane” resilience posture - Vendor documentation claims no ongoing connectivity to Defined’s cloud is required for the overlay to function, avoiding putting the coordination service in the critical path. - Strong cost/performance positioning - $1/host/month is materially cheaper than many alternatives in the “secure connectivity” category, particularly when user counts are high but host counts are manageable—or when you compare to seat-based models. - Vendor credibility signals - Publishing “Nebula is not the fastest mesh VPN” is an uncommon stance in vendor marketing and suggests a more engineering-led message—though the benchmark is still vendor-run and not independent.

Why customers chose this product (inferred from docs + community patterns)

- Likely selection drivers (based on product design and typical overlay-network buyer behavior): - Want Nebula’s architecture (p2p, encrypted overlay, NAT traversal/relays) but not the operational burden of CA + config distribution. - Prefer **per-host** pricing (can be cheaper than seat-based pricing in some orgs). - Want to keep network traffic off vendor relays/control plane (Defined claims the overlay continues functioning even if Managed Nebula is unavailable, though new connections/config changes may be affected).

03Field reports

- Public case studies with named customers and quantified outcomes were not found in the pages accessed. - Vendor blog includes technical guides and architecture explanations (useful for evaluation) but does not substitute for independently validated ROI claims. - What can be evaluated critically from vendor docs: - Architectural resilience claim: - Vendor asserts the overlay network does not require ongoing connectivity to Defined Networking’s cloud to function, and warns that some architectures put coordination servers in the critical path. - This design can reduce operational risk compared to solutions that rely on a central control plane for every connection establishment. - Methodology gap: - “Guaranteed uptime” is listed in Pro plan pricing, but an explicit public SLA document and status page were not found in sources accessed.

Important caveat on “review platform” coverage

Major enterprise review sites (G2, TrustRadius, Gartner Peer Insights) did not surface easily accessible, product-specific review pages for Defined Networking / Managed Nebula during this research.
A “Trustburn” listing exists with a numeric rating and review count, but Trustburn is not a widely accepted B2B decision platform on the level of Gartner Peer Insights/G2/TrustRadius; treat it as weak signal.

Community/social evidence (higher signal here)

- Reddit / homelab community (example) - A user in r/homelab stated: “I have been using Defined Networking (managed nebula) for the past year or so.” - While this indicates real usage, the snippet available in the accessible view does not include a full structured pros/cons breakdown. - Hacker News discussion (Nebula performance / expectations) - A Hacker News thread discusses Defined Networking’s benchmarking post “Nebula is not the fastest mesh VPN…” and community commentary about performance expectations in mesh VPNs.

Vendor-published “what others are saying”

The vendor “About” page contains a section titled “What others are saying about Nebula and Defined,” but these are curated testimonials/links and should be treated as marketing-selected unless validated independently.

Why some customers may leave (inferred; limited direct churn evidence)

Common churn reasons in this category (mesh/overlay networking):
- Need a larger “platform” (ZTNA suites, device posture, broader enterprise compliance, or integrated features) and migrate to more enterprise-heavy vendors.
- Prefer seat-based IAM-driven access controls for human users (Tailscale is strong here), versus host-centric overlays.

04Best fit

- Company sizes - Likely best fit: - SMB to mid-market: ~50–2,000 employees - Infra-heavy orgs where “hosts” scale faster than “people” (or where per-host cost optimization matters) - Enterprise fit is plausible but may depend on security/compliance requirements because certifications and regional hosting specifics are not prominently published. - Industries and verticals - Strongest alignment: - SaaS, dev tools, infrastructure companies - Teams running hybrid/multi-cloud and needing consistent private connectivity between nodes - Roles and personas - Decision makers - Head of Infrastructure, Platform Engineering Lead, DevOps Lead - Security Engineering (if positioned as zero-trust overlay) - End users - SREs, platform engineers, systems engineers - Pain points the product addresses - Reducing operational burden of: - Certificate authority management and certificate rotation - Distributing and updating host configuration at scale - Centralizing policy/firewall rules across a mesh overlay - Qualification criteria (great fit) - You want Nebula’s model but need a managed control plane. - You can operate a small amount of always-on infrastructure (lighthouses/relays) reliably. - You value the ability to export configs and run Nebula without the vendor cloud if needed. - Deal disqualifiers (poor fit) - You require published SOC 2/ISO certifications and detailed compliance collateral pre-purchase (not found publicly). - You need a vendor-operated relay/coordination layer as a fully managed service (Defined explicitly expects customers to run lighthouses/relays). - Your primary use case is workforce access governance with deep IAM device posture / endpoint compliance requirements.

05The pitch

- What the product does (core value proposition in objective terms) - Defined Networking sells **Managed Nebula**, a cloud-managed control plane for **Nebula**, an open-source, peer-to-peer encrypted overlay network originally built at Slack. - The product focuses on making Nebula operationally easier for teams by centralizing certificate authority (CA), host enrollment/config distribution, firewall policy management, SSO for admins, and audit logging—while keeping the **data plane** (actual overlay traffic) running on the customer’s own hosts. - Vendor positioning emphasizes “zero-trust overlay networking” for multi-cloud/hybrid connectivity and secure internal networking across distributed infrastructure. - Target market and market positioning - Primary buyers appear to be **engineering / infrastructure teams** that want a mesh-style private network for servers, workloads, and sometimes endpoints, without operating a full PKI and configuration distribution system themselves. - The “per-host” pricing, API-driven management, and documented architecture suggest a focus on **SMB → mid-market** infra teams and **cost-sensitive enterprises** that want a simple alternative to more complex SD-WAN/overlay suites. - Company background (founding year, HQ, key leadership) - Defined Networking was founded when **Nate and Ryan left Slack** to launch the company; the company states this occurred in **February 2020**. - Public-facing pages clearly identify the founders’ Slack background, but detailed HQ location and leadership roster are not prominently documented on the pages accessed in this research. - Funding and growth: investment rounds, acquisitions, estimated customer count/revenue if public - No reliable, primary-source funding totals or customer counts were found in the vendor’s official pages accessed here. - Third-party startup directories claim funding totals (example: “$18.9M”), but these listings are not primary financial disclosures and should be treated as **unverified** without corroboration from SEC filings, press releases, or reputable financial databases. - Pricing model with specific tiers and costs where available - Public, self-serve pricing is unusually transparent for infrastructure software: - **Free**: $0 per month per host, includes cloud-managed Nebula, up to **100 hosts**, up to **2 routes** for external hosts, SSO, and UI. - **Pro**: **$1 per month per host**, includes unlimited hosts, up to **100 routes**, priority support, and “guaranteed uptime”. - **Enterprise**: Contact sales; includes custom pricing, dedicated Slack support channel, and network design/setup. - Billing model clarifications: - “Hosts, lighthouses, and relays are all considered to be ‘hosts’ for billing purposes,” and enrolled hosts remain billable until blocked/deleted. - Total cost of ownership considerations (implementation, training, hidden costs) - Costs that may be “off the invoice”: - Operating your own **lighthouses and relays** (compute, bandwidth, monitoring, patching). - Ongoing **network design** work (CIDR decisions, segmentation model, routing strategy) that can be costly if you lack in-house network/infra expertise. - Process overhead for endpoint onboarding/offboarding and incident response (even with audit logs). - Vendor explicitly says it does **not** run lighthouses/relays for you, arguing you should control your own uptime; this can reduce vendor lock-in but increases customer operational responsibility. - Key competitors in the space (4–6 direct alternatives) - Tailscale (WireGuard-based mesh VPN + SaaS control plane) - ZeroTier (virtual networking / SDN-style overlay; often L2-like) - Netmaker (WireGuard mesh management; open source + SaaS) - OpenVPN (traditional VPN; not a mesh, but commonly considered in evaluations) - Headscale (self-hosted control plane alternative for Tailscale; community-driven) - Traditional SD-WAN / overlay offerings (varies widely; often heavier-weight than Nebula-style overlays)

Get a comprehensive analysis of Defined Networking including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →