Over recent years, ‘cloud-native’ service providers have developed ways to build and run massive data centers with a high degree of automation, to reduce operational overheads and deliver levels of service agility beyond traditional carrier infrastructure. RtBrick’s open disaggregated Peering Router brings these same benefits to ISP networks, by using agile methodologies and the same battle-hardened DevOps cloud automation tools that have been adopted by the world’s biggest cloud providers.
The RtBrick Peering Router is delivered as a software container, packaged out-of-the-box with the Open Network Linux (ONL) provided by the hardware SKU manufacturers, which handles peripherals such as LEDs, temperature sensors, and so on. The RtBrick Peering Router software runs on a choice of low-cost but powerful bare-metal switches.

RtBrick’s disaggregated Peering Router delivers some significant benefits compared to traditional monolithic systems:
Agility
ZTP (Zero-Touch-Provisioning) ensures that each switch is booted, provisioned and operational without requiring manual intervention. This means that you can add capacity, or roll-out new service features, in a matter of minutes instead of days or weeks. The software itself is developed using Agile methodologies so that features are rapidly prototyped and implemented, reducing the time-to-market for new services.
Reduced risk
RtBrick’s Peering Router software is compiled for your specific use-case, using only the features you need. With an order of magnitude fewer lines of code, and a single state database rather than hundreds, the whole system is less complex, less prone to bugs and has much faster restart times. It also allows you to pick and mix between the latest silicon and the best available software. It also includes a number of critical security features detailed below.
Cloud cost-levels
Now you can take advantage of the low cost-points of merchant silicon on your choice of bare-metal switches, significantly reducing your capex bill. And opex costs can be reduced by automating your operations, using ZTP and the same Web2.0 operational tools that the ‘cloud-natives’ use to run their infrastructure.
The Peering router's capacity can be scaled down to a single RU bare-metal switch or a more powerful 2RU switch with interfaces up to 400Gbps.

Single RU bare metal switch example
Along with a traditional CLI, RtBrick’s Management API has been designed to simplify the integration with your existing OSS and BSS systems. It reduces the amount of time and effort required to make your disaggregated network operational, and it leverages widely-adopted industry tools and programming languages. RtBrick’s API is ‘consumer-driven’ – which means you can use the formats and languages of your choice, rather than have them imposed on you by a vendor. This allows you to build a client in Python, Go or Java, for example, as you prefer. And the APIs are all edited in Swagger, which is also a widely understood tool used by developers. RtBrick’s Management API actually comprises of several underlying APIs, which each follow the same consumer-driven approach.
The features supported by RtBrick FullStack are expanding all the time, because it's much faster for us to add and test new features than it is using a traditional monolithic code base. You can see our current feature list on our latest data sheet.
RtBrick's Full Stack routing software can operate on many bare metal switches, depending on your performance and port count requirements. You can find details of compatible hardware here.