Routerly v0.1.0 – Architecture and Platform Baseline

Summary

Routerly v0.1.0 establishes the architectural and operational baseline for the project. This release does not introduce a full routing implementation, but defines the control-plane model, platform assumptions, and deployment strategy that all future Routerly work will follow.

This marks the transition of Routerly from an idea to a structured platform.

Highlights

• Defined Routerly as a snap-delivered routing control plane
• Established Ubuntu Core as the primary deployment platform
• Documented the separation between control plane, routing engine (FRR), and Linux data plane
• Introduced configuration-first and rollback-safe design principles

Changes

Added

• Public architecture documentation
• Initial Hugo site with blog, docs, and design documentation
• Release and design documentation workflows

Changed

• Project scope clarified away from “router OS” toward “routing control plane”

Fixed

• N/A (no runtime components yet)

Removed / Deprecated

• Early language implying Routerly would replace the operating system

Upgrade Notes

Not applicable. This is the first baseline release.

Known Issues

• Routerly does not yet provide a functional routing implementation
• CLI, snap, and control plane services are still under development

What’s Next

• Implement the first working control plane prototype
• Define the configuration model
• Begin integrating FRR and Linux networking primitives through Routerly