House Tracker

Local todayCloudflare Pages soon

About House Tracker

A quiet place for Nate and his partner to watch the houses they’re considering — live Zillow-sourced listings, photos, and price history against a $700K budget. Built for the two of them now; meant to be something their realtor can open later too.

Open the dashboard Add a house

What it is

House Tracker is a small dashboard of homes they’re actually looking at. Pick an address, see the listing details, a Zillow photo (or a map if the photo is missing), and an interactive price chart with a $700,000 line so it’s obvious what’s over or under budget.

A separate House Tracker bot scrapes Zillow, updates a Google Sheet, and commits one JSON file per house into this GitHub repo. The web app just reads those files. New listings show up after a git pull; Sunday price runs keep the history current.

Who it’s for

Today: Nate and his partner, running the app on a laptop with npm start. Nobody else can reach it.

Soon: the same dashboard for their real estate agent — browse the list, check prices against budget, and suggest a listing with Add House. Visitors can still see this public About page; the houses themselves stay behind a shared password Nate can hand the realtor.

How the pieces fit

Planned shape: Cloudflare Pages serves this public landing plus a password-gated app. The bot still writes JSON to GitHub; Pages rebuilds from the repo. Right now the same UI is just Express on Nate’s laptop.

Anyone can open the public About page. Nate and the realtor unlock the dashboard with a shared password. Cloudflare Pages (today: npm start on a laptop) reads data/houses/*.json from GitHub. Add House posts a Zillow link or address to the House Tracker bot, which scrapes Zillow, updates a Google Sheet, and commits JSON — including Sunday price updates — back to the repo so the dashboard stays fresh.

Coming soon

Honest status: this is a local app. Hosting, public landing, and realtor access are the plan — not live yet.

  1. Host on Cloudflare Pages

    Ship the site from Pages, not a home-laptop tunnel or Tailscale expose. GitHub stays the source of truth; a push (including the bot’s JSON commits) rebuilds the site.

  2. A public, portfolio-style landing

    This About page can be that landing — or lead into it. Anyone may see what the project is. House details and the dashboard are not part of that public surface.

  3. A simple password box, not Cloudflare Access

    The dashboard and listing data sit behind a small client-side password prompt. Nate shares that password with the realtor. No extra identity product, and no password written down on this page.

  4. Realtor on the same dashboard

    Once it’s hosted, the agent can open it from a phone or laptop, scan the same budget chart, and suggest houses through Add House — same webhook, same bot, same JSON files.

Take a look

The dashboard and Add House form are here on this machine today.

Dashboard Add house