noBGP replaces legacy internet routing protocols like BGP and VPNs with a programmable, private networking fabric. It eliminates public exposure, manual configuration, and unpredictable data paths.
Routers direct traffic between noBGP components. To create a deterministic data path between your endpoints, you may need multiple routers to direct data to specific paths, dark fiber, or data sovereignty.
noBGP keeps your workloads completely private—no public IPs, no open ports, and no external visibility. It’s a “dark network” that only trusted services can access through identity-based policies.
noBGP completely removes the issue of IP conflicts by abstracting IP identity from routing logic. Multiple overlapping subnets can coexist without the need for NAT or IP renumbering.
No. noBGP overlays your existing infrastructure without requiring changes to your IP address scheme, VPC layouts, or cloud provider. It works across AWS, GCP, Azure, on-prem, and even edge devices.
Deterministic data paths mean your data always takes the exact route you define—no surprises, no guesswork. With noBGP, you control how and where your data travels, ensuring consistent performance, compliance, and security every time.
Data passes through noBGP routers, so the more routers you have the more flexibility on creating routing paths.
Deployment is fully automated using infrastructure-as-code tools like Terraform. You define services or endpoints you want to connect, and noBGP handles the secure, private pathing between them.
The free evaluation plan includes all features of noBGP, allowing you to assess its simplicity, security, and value.Limitations:
* Not intended for production workloads
* Email-only support
* Potential bandwidth throttling for excessive usage
Have specific evaluation needs? Contact us, and we'll ensure you can test your required use cases effectively.
noBGP removes the need for VPN tunnels, VPC peering, NAT gateways, MTU adjustments, IPv4/IPv6 translation, and static route tables—replacing all with simple, programmatic deployment.
A node is any location noBGP software is installed. The software can be configured as a bridge, proxy, or gateway. Installing a bridges in two different VPCs so they can communicate with each other is counted as two nodes. Self hosted routers or noBGP SaaS routers are not counted as nodes.
A router is a software component that connects noBGP components (bridges, gateways, or proxies). Routers privately direct traffic across clouds, regions, or networks without exposing an organizations private resources to the public. Routers can be self-hosted or part of the noBGP SaaS network.
Unlike a VPN, which creates a secure tunnel between networks but still relies on manual configuration and IP-based access control, noBGP provides identity-based, programmatic routing between workloads without exposing private IPs or requiring NAT, firewall rules, or peering. It enables service-level connectivity across clouds and environments, eliminating the need for subnet coordination or centralized gateways.
Yes. noBGP creates private, encrypted, identity-based connections across clouds, regions, and on-prem locations—without exposing public IPs or requiring NAT gateways or VPNs.
Public BGP routing exposes your infrastructure to the open internet, lacks deterministic control, and is prone to hijacks, leaks, and misconfigurations. noBGP replaces this with a private, programmable routing layer that ensures secure, direct service-to-service communication without public IPs or complex config.
As an early adopter, we're offering everyone that registers today, a free SaaS account.
REGISTER FOR FREE ACCOUNT
