AutoPeer

An open source system that helps network operators automate their internet peering. Facilitating secure inter-operator intent via API. AutoPeer is authored by Antonio Faria, governed as a benevolent dictatorship, and distributed under license.

Warning

AutoPeer is in construction, during this time no effort shall be afforded to migrations and backwards compatibility.

Internet peering for over a decade has typically been negotiated through email, and larger network operators have addressed its limitations through organically developed portals. In 2023 a working group comprised of Jenny Ramseyer (Meta), Matt Griswold (FullCtl) and Erica Salvaneschi (Cloudflare) proposed Peering API, their work can be found here. The fundamental principle, adopted as AutoPeer's mission is by each network operator employing a standardised API, bidirectional system-to-system internet peering negotiation can be facilitated.

Note

AutoPeer and Peering API schemas do not align, although its the author's intention to broach the discussion with the working group.

AutoPeer aims to address most of the technical tribulations, a few of its features are:

• High-performance, event-driven, microservices architecture¹.
• Horizontally scalable².
• Reliable, stable and consistent.
• First-class integrations.
• Feature-packed services.³

Installation

Our installation guide will be published soon.

Versioning

Releases will follow semantic versioning (major.minor.patch).

Contributing

Suggest a feature or report a bug. Read our developer guide.

License

AutoPeer is distributed under the Apache 2.0 license.

Footnotes

1. That's a bingo! ↩

2. Not yet available for Dispatcher service. ↩

3. AutoPeer helps network operators define their internet peering policies and rules for automated resource validation. ↩