IPAM Lite
Somewhere to keep an address plan: subnets, gateways, DHCP scopes and the static assignments that everyone forgets. Checked continuously, saved to a file you control.
Local toolYour network plan stays in your browser. Nothing you enter is uploaded, logged, or sent to any server.
Static addresses — printers, cameras, servers, anything that must not move. These are what a spreadsheet loses track of first.
The plan is a JSON file. Export it into your own documentation or version control; import it back on any machine. There is no account and no server copy.
What it checks, and what it deliberately does not do
Every change re-runs the whole plan through the shared validation engine: overlapping subnets, duplicate VLAN IDs, gateways outside their subnet or on a reserved address, DHCP ranges that fall outside the subnet or cover the gateway, static assignments sitting inside a DHCP pool, duplicate addresses, and subnets running out of room.
VRFs are respected. Two subnets may use the same address space when they are in different VRFs — that is what a VRF is for — and the same is true of individual addresses. Overlap within one VRF is still reported.
It does not talk to your network. Nothing is scanned, pinged or discovered. This records what you intend, which is a different and more durable thing than what happens to be responding today. A real IPAM that polls devices is a server application; this is the document.
Storage is off by default. Nothing is written to your browser's storage unless you tick the box, and even then it stays on that machine. The reliable way to keep a plan is to export the JSON and put it wherever your other documentation lives.
Related tools
VLAN + Subnet Designer generates a scheme to start from. VLSM Designer does the allocation arithmetic. Subnet Calculator inspects any prefix.