Use Case
Multi-Site Network Management
Manage infrastructure records across multiple locations. Organize sites, devices, subnets, and WAN circuits with shared access and a complete change history.
For organizations with offices, branches, or data centers in several locations, multi-site connectivity is only part of the job. Teams also need accurate records of each site, its devices and subnets, and the WAN circuits that connect locations. Obelinf brings that inventory together, maps point-to-point circuits in network topology, and records who changed what. Use it alongside the systems that provision links and monitor live network performance.
Manage infrastructure across every location.
Frankfurt DC
Germany · Europe/Berlin
London Office
United Kingdom · Europe/London
Singapore DC
Singapore · Asia/Singapore
Document the links between sites.
MPLS-NYC-LON
MPLSNew York → London
DIA-ORD-SJC
DIAChicago → San Jose
BB-MIA-ATL
BroadbandMiami → Atlanta
Your team, your rules.
Alex Johnson
alex@acme
Jordan Lee
jordan@acme
Sam Patel
sam@acme
How it compares
Teams managing multiple locations can use spreadsheets, a self-hosted platform, or a shared infrastructure inventory. Here is how the approaches compare for site records, WAN circuits, access, and change history.
| Spreadsheets | NetBox | ObelinfOur pick | |
|---|---|---|---|
| Multi-site view | Partial | Yes | Single source of truth |
| Circuit tracking | Manual | Plugin | Built-in |
| Access control | None | Role-based | Roles + immutable log |
| Visual topology | No | Plugin | Automatic |
| Audit trail | None | Built-in | Immutable + field-level |
| Search | Manual | Yes | Built-in |
| Setup time | Instant, then stale | Hours to days | Minutes |
| Cost | Free (your time) | Free, self-hosted | Free to $299/mo |