← Selected work

Personal build · Personal developer utility

A menu-bar IP monitor for when a changing home connection meets a strict database allowlist.

Living in the Sierra foothills means spotty internet, limited provider choices, and no practical static IP. When a new client’s database allowed access only from approved addresses, I built IPTracker to make the changing address visible and actionable instead of a recurring trip through whatismyip.com and the Azure portal.

Role
Creator and desktop app developer
Context
Residential internet with restricted database access
Disclosure
Personal project

The problem

The problem

A residential connection that changes its public IP is usually a minor inconvenience. It becomes a real interruption when a client’s Azure database allows only specific addresses. The old routine was repetitive and brittle: check whatismyip.com, copy the value, find the correct Azure resource, then update the allowlist before getting back to work.

What I built

The system, not just the screen.

A quiet check that makes the important change visible

Built a configurable background check that fetches the current public IP every minute by default and keeps it in the macOS menu bar. When the address changes, the app sends a small notification instead of leaving the next failed connection to reveal the problem.

The context needed for the next action

Added a one-click copy action and current-region information to the menu. The app is deliberately narrow: it turns the “what is my IP?” step into a glance, so updating an approved Azure database address is the only remaining work.

A personal utility that can still improve itself

Built it with NativePHP and its auto-update system, publishing artifacts to DigitalOcean Spaces so installed copies can receive improvements. A handful of people use it now; the next iteration will let someone run a chosen shell script after an IP change, including my update-azure-ip command for the Azure work.

System sketch

How the system works.

A simplified view of the system boundary and the work it moves through.

  1. Public IP check
  2. Change detection
  3. Menu-bar status
  4. Copy or notification
  5. Database allowlist update

Key decisions

Key decisions

  1. Use a native menu-bar utility because the information should be nearby but never demand a full application window.
  2. Notify only when the address changes, keeping the utility useful without creating another noisy monitoring surface.
  3. Leave provider-specific automation optional: copy and context work for anyone, while a script hook can handle a personal or team-specific allowlist workflow.

What it enables

What it enables

IPTracker converts an unpredictable home-network constraint into a small, visible workflow. For me it removes the manual lookup that used to precede every Azure allowlist update; for its small group of users, it makes a changing IP much less mysterious.

Return to selected work

Similar problem?

Facing a similar kind of product or systems problem?

Tell me where the complexity is piling up. If there’s a strong fit, I’ll reply personally.

A few sentences is plenty.

Your note goes straight to me—no mailing list.