Obelinf

Obelinf combines IP address management (IPAM), device inventory, data center infrastructure management, network topology, rack management, cable tracking, VLAN and VRF management, and infrastructure audit history. Its IPAM tools cover hierarchical subnets, VRF modeling, VLAN mapping, address status, reservations, and live utilization. Interactive topology diagrams provide site-aware views and cable-path tracing; rack tools show elevations, U-positions, reservations, and utilization across a fleet. The REST API and scoped, revocable keys support automation and third-party tools. An MCP endpoint lets Claude, Cursor, and other compatible assistants query and update records using scoped keys. The maker says create, update, and delete activity is recorded with user, timestamp, context, and field-level changes. Personal is free and includes up to 30 devices, four racks, five subnets, 100 IP addresses, 25 cables, and 10 VLANs; VMs and clusters require a paid plan. Teams costs $99/mo and Scale costs $299/mo. Paid plans have a 14-day trial requiring a credit card. Obelinf is available on web and through an API.

Obelinf brings inventory, IPAM, topology, and rack management into one platform, with API and assistant integrations for record access. The free plan has specified capacity limits, while paid plans add room for larger teams and deployments.

Obelinf suits network engineers, infrastructure teams, and IT administrators managing physical or virtual infrastructure. The maker describes use from homelabs to multi-site enterprise deployments.

Obelinf is a web and API platform for keeping IP addresses, devices, racks, cabling, topology, and infrastructure history in one model. It fits network engineers, infrastructure teams, and IT administrators whose environments span physical and virtual equipment, from a homelab to multiple sites. The strongest case is connected documentation; the main caution is that capacity and collaboration limits arrive quickly on lower tiers.

Overview

Obelinf combines IPAM, DCIM-style device inventory, network diagrams, rack planning, cable and circuit tracking, VLAN and VRF management, relationship mapping, and an infrastructure audit trail. That breadth matters when a team needs to follow an address to its VLAN, device, rack position, and cable path without reconciling separate systems.

The service covers physical and virtual infrastructure, but virtual machines and clusters require a paid plan. A free homelab plan needs no self-hosting, making it a low-friction way to establish records without maintaining another server.

Key features

IPAM handles hierarchical subnets, VRF models, VLAN mapping, address-status tracking, reservations, and live utilization. These controls are useful for teams managing segmented networks and capacity, rather than merely storing a list of addresses.

Obelinf creates interactive, site-aware topology diagrams from infrastructure documentation and supports cable-path tracing. Rack tools provide interactive elevations, true U-position tracking, reservations, and fleet-wide utilization views. Combined with device inventory, cable tracking, and circuit management, that gives physical-infrastructure teams a more complete operational picture than an IPAM-only product.

Changes are recorded in an audit history: create, update, and delete actions include the user, timestamp, context, and field-level changes. The REST API and scoped, revocable API keys support automation and third-party tools. An MCP endpoint lets Claude, Cursor, and other MCP-capable assistants query and update records with scoped keys; that can speed record access, but it also makes careful key management important.

Pricing

Personal: free, billed $0/mo. It includes one user, one organization, one site, four racks, 30 devices, and community support. The broader free-plan caps are five subnets, 100 IP addresses, 25 cables, and 10 VLANs. This is a sensible starting point for a homelab or a very small environment, but the single-user structure and tight quotas limit team documentation.

Teams: $99 a month, billed $99/mo. It supports up to 10 team members, three organizations, 10 sites, and 200 devices, with priority support. This is the practical entry point for a small operations group that has outgrown Personal and needs shared access across several locations.

Scale: $299 a month, billed $299/mo. It raises capacity to 50 team members, 10 organizations, 100 sites, and 600 devices, and adds SSO and RBAC alongside priority support. Choose it when centralized access control and a distributed deployment matter; it is a substantial jump from Teams for organizations that do not need those controls.

Enterprise: custom pricing, with unlimited team members, organizations, sites, and devices plus dedicated support. It is aimed at large deployments whose requirements exceed the fixed tiers.

Paid plans include a 14-day trial of the selected tier and require a credit card to start. Stripe processes payments; Obelinf says it does not retain card details on its servers, and Stripe is PCI Level 1 certified. Personal has community support, Teams and Scale have priority support, and Enterprise has dedicated support.

Platforms

Obelinf is delivered through a web interface and an API. The REST API, scoped keys, and MCP endpoint make it suitable for integrations and assistant-driven record work, while the web platform provides the primary documentation workspace.

Who it's for

Network engineers benefit from the linked IPAM, VLAN, VRF, topology, and cable records. Infrastructure teams managing racks, circuits, and multiple sites gain a shared physical-and-logical view. IT administrators can use the audit history and access controls when change accountability matters. Personal is most appropriate for an individual homelab or small test environment; Teams suits collaborative operations; Scale and Enterprise fit larger, distributed organizations.

Pros and cons

Pros

• Connected infrastructure model: IPAM, inventory, topology, racks, cables, and circuits are represented together.
• Useful network detail: Hierarchical subnets, VRFs, VLANs, reservations, and live utilization support real allocation work.
• Automation options: A REST API, revocable scoped keys, and MCP integrations cover both conventional tools and capable assistants.
• Accountability: Field-level audit history records who changed what and when.
• Accessible starting point: Personal is free and does not require self-hosting.

Cons

• Free-tier ceilings: One user, 30 devices, four racks, and other small quotas make Personal unsuitable for growing teams.
• Paid-only virtual resources: Virtual machines and clusters are unavailable on the free plan.
• Paid entry cost: Teams starts at $99 per month, with Scale rising to $299 per month for SSO, RBAC, and larger limits.
• Assistant access needs governance: MCP agents can update records, so scoped and revocable keys should be managed as operational credentials.

Alternatives

For a broader directory of comparable tools, see Network Documentation Software and IP Address Management Software.

Choose Hudu instead if you want a paid documentation product with Android, iOS, web, API, extension, and self-hosted platforms; it starts at $30 a month with no user minimums.

IT Glue is another paid documentation option, with a Basic plan at $29 per user per month on a 36-month term and a five-user minimum.

Pick NinjaOne when endpoint-management coverage is the priority; its endpoint plan starts at $1.50 per device per month at 10,000 endpoints.

Open Network Diagram is a free, self-hosted Docker deployment under GNU GPL v3 for teams focused on network diagrams.

Scanopy offers a free self-hosted Community Edition for one network and one user, with paid tiers beyond that.

GestióIP is a free IPAM-focused option, with configuration management sold separately.

LOGINventory provides a forever-free tier for up to 20 devices and paid inventory editions.

Nautobot is a self-managed, open-source-oriented alternative with a free Community edition.

Verdict

Obelinf is a strong choice for teams that want IPAM, inventory, topology, rack, and audit records tied together, with API and MCP access for automation. Start with Personal for a small homelab, move to Teams for shared operations, and choose Scale when SSO, RBAC, or broader capacity is essential. Look elsewhere if you need a much larger free tier, endpoint management first, or a self-hosted open-source deployment.