IP address management for lean IT teams

Live IP inventory, without the DDI project.

Discover what is using every address, keep ownership and history beside the evidence, and answer network questions without rebuilding your stack.

Sign-ups opening soonSee the real product

No card · Linux agent · Outbound HTTPS · One /24 free forever

Observed subnet / 192.168.10.0/24192.168.10.18online · switch
No applianceOne lightweight Linux agent
Outbound onlyCloud connection over HTTPS 443
Priced by subnetNot by every discovered device
Works alongside DDIKeep existing DNS and DHCP
Actual product · anonymized data

The network changes. Your inventory changes with it.

Search IP, MAC, hostname, vendor, OS, owner, and recent state from one workspace. Click the screen to inspect the real interface.

01 / Observe

See what is actually present

Active discovery records IP and MAC evidence. Paid plans can add continuous passive listening and faster scan intervals.

02 / Explain

Keep the context beside it

Add device names, owners, notes, reservations, DHCP clues, first seen, last seen, and recent changes.

03 / Act

Move from evidence to action

Search, export, alert, scan, or use scoped admin controls when the plan and platform support them.

Daily operating loop

Answers that survive the next network change.

Discovery provides evidence. Your team adds the context only people know. The result stays useful during incidents, handovers, and audits.

01

“What is that IP?”

Search across address, hardware identity, hostname, vendor, operating system clues, owner, and notes instead of checking separate records.

IPMACHOSTNAMEOWNERVENDOR
02

“What changed?”

Use first-seen, last-seen, online and offline state, and recent activity to distinguish a new device from an old record.

FIRST SEENLAST ONLINERECENT LOGS
03

“Can I use this address?”

Review observed state, DHCP data known to ipuipu, reservations, bindings, and recent activity. Free-IP suggestions remain candidates, not absolute guarantees.

DHCP CLUERESERVATIONRECENT EVIDENCE
A deliberately different scope

More current than a spreadsheet. Lighter than enterprise DDI.

ipuipu is built for observed LAN operations. It complements authoritative infrastructure rather than pretending to replace everything.

DecisionSpreadsheetipuipuTraditional DDI / IPAM
Primary jobManual recordDocument what people already knowLive LAN operationsObserved inventory plus team contextInfrastructure controlAuthoritative DNS, DHCP, and IPAM
DeploymentImmediateNo discovery or network evidenceLightweightLinux agent and outbound HTTPSProject-scaleBroader integrations and governance
FreshnessRemember to updateAccuracy follows process disciplineObserved repeatedlyEvidence refreshes with the networkAuthoritative by designBest when centrally managed
Cost modelTool cost is lowHuman upkeep is the tradeoffPer /24 managedNo charge for every discovered deviceVendor-specificUsually tied to broader scope
Best fitSmall and staticFew changes, one clear ownerLean and distributedChanging LANs, limited operator timeComplex enterpriseCentral DDI is the requirement
Honest boundary

ipuipu is not authoritative DDI and optional Linux enforcement is not full NAC. Use a switch, firewall, NAC, or another dedicated enforcement point when complete same-subnet isolation is required.

Built for the operator doing the work

A strong fit when the network is larger than the team.

Not every company needs an enterprise DDI program. Many still need a dependable answer when somebody asks what is connected.

01 / Lean internal IT

One shared operational memory

Give a one-to-ten-person team a current place for identity, ownership, availability, and recent change.

02 / Multi-site operations

Consistent visibility across locations

Organize office, branch, studio, clinic, lab, or factory subnets without paying for every endpoint.

03 / Spreadsheet migration

Keep the context. Automate the evidence.

Preserve names, owners, notes, and reservations while discovery handles the facts that change underneath them.

Optional AI / MCP · Paid

Ask the inventory. Keep the evidence attached.

Remote MCP and API access can answer scoped questions about IPs, MACs, owners, recent activity, and low-conflict free-IP candidates. AI is the interface, not the source of truth.

Access can be limited by role and instance. Block and unblock requests require an impact preview, administrator permission, and explicit confirmation.

ipuipu / evidence queryscoped · read
Find low-conflict free IP candidates. Check DHCP, static allocations, reservations, and recent logs first.

Three candidates found. These are evidence-backed candidates, not absolute guarantees.

192.168.1.37never seen · outside known DHCP pool
192.168.1.105last seen 45 days ago · no recent logs
192.168.1.156marked free · no recent activity
Security and control

Start with visibility. Turn on action deliberately.

The inventory is useful before enforcement is enabled. Operational actions remain scoped, explicit, and reviewable.

01

Outbound cloud connection

The agent communicates over outbound HTTPS 443. No internet-facing inbound rule is required.

02

Selected local scope

Discovery stays within the instances and subnets you choose instead of scanning arbitrary external ranges.

03

Scoped access

Limit API and Remote MCP access by role and instance scope.

04

Explicit write controls

Administrative network actions require the right role, an impact preview, and confirmation.

Simple, visible pricing

Pay for managed subnet scope, not device count.

Start with one /24 free forever. Upgrade when you need more subnets, shorter intervals, longer history, or advanced operations.

FreeStart here
$0

Forever for one /24. No credit card required.

  • Managed scopeOne /24
  • IP and MAC inventoryIncluded
  • Owners, names, and notesIncluded
  • Log history3 days
  • Active scan interval10 minutes
  • Passive listeningNot included
  • Remote MCP / APINot included
Sign-ups opening soon
One /24 free foreverAnnual option saves two monthsCancel anytimeNo per-device pricing
Start with visibility

Replace the spreadsheet, not your whole network stack.

Install the Linux agent, let evidence build the first inventory, and add the context your team already carries.

Sign-ups opening soonPublic sign-ups opening soon