Protocol-agnostic core YANG per subsystem BGP, interfaces, FIB CLI, SSH, web, API, MCP Compiled or external plugins AGPLv3 source

Latest news

All updates
Recently shipped

Week of 2026-08-03

Ze is being checked against the RFCs it implements, one MUST at a time, and that is where most of this…

Evidence

Tests, fuzzing, and interop before release claims.

These counts show what backs Ze before you spend time on a lab. The interop list names the peer daemons used in the protocol checks.

Run a BGP lab Read the evidence map
22,200+ unit tests
  • Wire encoding, parsing
  • Config, FSM, plugins
  • gomu mutates code to check assertions
 1,500+ end to end tests
  • Peering, sessions, updates
  • Editor, commits, reloads
  • Commands checked as operators run them
 78 fuzz targets
  • Parsers, external inputs
  • Wire formats, config files
  • Saved crashes become regression cases
 9 interop targets
  • Real third-party daemons
  • BGP sessions in Docker
  • Routes checked by peer CLIs
Tested against routing stacks FRR BIRD GoBGP OpenBGPd FreeRtr RustyBGP rustbgpd ExaBGP migration path

Run it as a lab, daemon, or appliance.

The same binary and configuration support each path, from a Docker lab to spare hardware.

Lab

Run a BGP lab

The reproducible interop lab runs Ze beside real BGP daemons, establishes sessions, and checks routes through each peer's own CLI.

Docker FRR BIRD GoBGP
Run lab BGP interop
Daemon

Run as a daemon

Ze runs on any existing Linux distro, managed by systemd or your chosen process manager. This is the easiest route when Ze has to fit into infrastructure you already run.

Existing Linux systemd-ready
Quickstart two BGP peers
Appliance

Run as an appliance

A bootable gokrazy image for appliance hardware: read-only root filesystem, no shell, no package manager, and automatic process supervision.

gokrazy image Read-only root filesystem
Install guide PXE, ISO, or Ventoy

Why Ze.

Ze keeps the core protocol-agnostic. Subsystems bring their own YANG, and the CLI, web editor, validation, generated references, and MCP tools are derived from the resulting schema.

Model

One model feeds every interface

Each subsystem declares YANG. The config tree, validation, CLI completion, web editor, API, MCP, docs, audit, and diagnostics read that model.

Runtime

Small core, registered subsystems

The core holds the supervisor, message bus, config provider, and plugin manager. BGP and interface management register into it.

Routing

Network OS built on the engine

The shipped daemon speaks BGP, manages Linux interfaces, programs the FIB, and serves its configuration through SSH and the web UI.

Honest

Plugins keep their own contract

Plugins can be compiled Go modules or external processes. Compiled modules load their YANG into the daemon validator; external plugins can expose their model through ze schema.

Generated references are part of the product.

Read the generated references before you run Ze.

Ze is an open-source configuration and protocol engine. The network operating system built on it speaks BGP, manages Linux interfaces, programs the FIB, and serves the same YANG-modeled configuration through SSH, web, API, and MCP.

Operate (6) Routing (9) Services (9) Automate (7) Observe (9) Secure (5) Platform (6)

First paths for routing feedback.

The BGP lab, ExaBGP migration, and appliance install are good starting points.

quickstart.sh 
# build from source
$ git clone https://github.com/ze-software/ze.git
$ cd ze && make build

# set up credentials and configure
$ bin/ze init
$ bin/ze config import router.conf

# start
$ bin/ze start

# from another terminal
$ bin/ze cli -c "show bgp peer list"
$ bin/ze cli -c "monitor event"
Good starting points

A lab peer, a migrated ExaBGP config, or a looking-glass instance can produce useful reports from people who know routing operations.

BGP interop lab FRR, BIRD, and GoBGP in Docker ExaBGP migration try an existing config and process script Appliance install ISO media, PXE provisioning, spare hardware Looking glass publish read-only BGP visibility AI-assisted operations MCP exposes Ze commands to tools
FAQ answers before you try Ze Project status what works and what may change Ask on Discord talk to the project before a lab build

Safe ways to try Ze before the first release.

Ze is early enough that routing feedback can still change the system. These cards give each reader a low-risk starting point.

IXP

Route server

IXP operators can run the route-server lab first and compare policy behaviour before touching members.

Peering Policy Replay
Route server policy and replay
Lab

Lab router

Network builders can bring up two BGP peers, inspect routes, and check whether Ze's operator tools fit their workflow.

Quickstart BGP peers
Quickstart two peer lab
Migration

ExaBGP replacement

ExaBGP users can try the migrator against an existing config and see which process scripts still translate cleanly.

Migration Plugins
Migration path config and process scripts
Appliance

White-box appliance

People with spare x86 hardware can boot the appliance image and test the same configuration model without a general-purpose shell.

ISO PXE gokrazy
Appliance guide spare hardware
Observe

Looking glass

Operators who need read-only BGP visibility can publish a looking glass and inspect routes without giving shell access.

Read-only BGP visibility
Looking glass read-only BGP
Interop

Protocol testbed

Protocol implementers can run Docker interop scenarios against FRR, BIRD, and GoBGP, then turn a failure into a test case.

Interop Docker
Interop lab real peer daemons
MCP

AI-assisted operations

MCP exposes Ze commands and structured output to AI tools without a separate command set.

MCP CLI catalogue
AI via MCP same command catalogue

Recent engineering notes.

Weekly updates come from git history and Discord's ze-news. They stay specific and technical.

See all updates
Try safely

Try Ze before the first release.

Start where a mistake cannot affect a live network.

Run a BGP lab Read the quickstart
Release Expected Q4 2026. No stable release has shipped yet, and configuration may change.
BGP lab Exercise Ze against FRR, BIRD, and GoBGP without touching a production router.
Migration Try the ExaBGP migration path against an existing config before changing automation.
Appliance Boot Ze on spare hardware with the same binary and configuration model as daemon mode.
Source Read the code, generated docs, RFC gate, and test evidence before deciding where Ze belongs.