Active Development • Q1 2026

Routing infrastructure that doesn't break under pressure

Built for environments where reliability isn't optional. Plain English commands, automatic rollback, and operational features from day one.

Latest blog posts

Progress notes, design decisions, and release milestones as Routerly evolves.

01

Hello Routerly

Tue Jan 13 2026

Why this project exists and what’s next.

Read the blog
Command Interface
Routerly CLI
$ routerly allow guest access to internet
$ routerly deny iot access to admin
$ # Plain English. No memorizing flags.

Operational requirements, not feature checklists

Every feature in Routerly exists because it solves a real problem in austere environments. No bloat, no unnecessary complexity.

01

Plain English Commands

When you're troubleshooting under pressure, you shouldn't need to remember cryptic flags. Commands that read like sentences reduce cognitive load and errors.

02

Automatic Rollback

Bad configs happen. Routerly tests connectivity after every change and automatically reverts if things break. No manual recovery, no lost access.

03

Built on Ubuntu Core

Immutable OS, transactional updates, automatic security patches. Designed for deployed edge devices where you can't just "reboot and fix it."

Design Philosophy

Informed by operational experience: Routerly's features come from real-world work with network infrastructure in tactical communications, secure edge deployments, and environments where reliability isn't negotiable.

Current status: Active development in Go. Building the routing core with operational reliability features: automatic rollback, health checks, security zone isolation, and audit logging from the start.

Deployment model: Distributed as a snap package. Designed for Ubuntu Core deployments where security, reliability, and automatic updates matter most.

Building in stages

Each phase focuses on core operational capabilities. No unnecessary features, just what actually matters in deployed environments.

✓ Q4 2024 - Q4 2025

Foundation & Research

Architecture design, Ubuntu Core integration, snap packaging strategy, command language development

→ Q1 2026

Core with Operational Features

Routing engine in Go with automatic rollback, health checks, security zones, and audit logging

Q2 2026

Tactical & Edge Features

QoS for bandwidth constraints, degraded mode operation, offline capability, fast failover

Q3 2026

Documentation & Scenarios

Deployment guides, security documentation, troubleshooting playbooks, reference architectures

Q4 2026 - Q1 2027

Production Hardening

Performance optimization, security audits, comprehensive testing, monitoring and telemetry

Q2 2027

Automation Support

REST API, declarative configs, Infrastructure-as-Code tooling

Q3 2027+

1.0 Release

Stable release, comprehensive documentation, professional support options