03 / Address intelligence

IPAM

Check the address. Prevent the conflict.

I built IPAM to collect address claims across a network overlay, flag overlapping ownership, and check candidates before allocation.

03 / ADDRESS ATLASInteractive demo

Interactive demo · sample data

192.0.2.42 is available in this fictional address map. Family ownership is checked before selection.

What I built

A safer next allocation.

I built IPAM to close the gap between an address that looks unused and an address that is actually safe to allocate. It brings claims from across the overlay into one searchable view.

What I delivered

A sweep engine covering inside NATs, node interfaces, virtual routes, and outside-NAT scopes.
An allocator that respects family blocks and checks candidates for conflicting claims.
A fabric-wide conflict audit, an append-only drift journal, and critical-overlap alerts.
Browser and command-line workflows backed by the same engine.

Why it matters

Ownership and conflicts are visible before a change is made. The audit and journal also make it possible to investigate what changed between syncs.

System architecture

Sweep

Collect every claim source

Normalize

Unify ownership and scope

Check

Family blocks + overlaps

Journal

Changes, audit, alerts