Personal project

House Board

A local-first workspace for comparing listings, modelling monthly costs, and keeping property research organised — in active development.

Overview

What it is

House Board is a small full-stack app I am building to support a major life decision: buying a home. It brings together listing data, running-cost assumptions, tax and income modelling, and a visual “board” view so comparisons stay honest and repeatable — not scattered across spreadsheets and browser tabs.

The focus is clarity: same inputs, same formulas, quick snapshots, and room to refine assumptions as I learn more.

Engineering

Stack & run

  • API: FastAPI (Python), SQLAlchemy/async SQLite for structured data, routers for houses, costs, income, rooms, calculations, and snapshots.
  • Web UI: React + Vite (TypeScript), proxied to the API in development.
  • Data: SQLite database for boards, inputs, and snapshots; optional enrichment from listing portals and area/council-tax style lookups where APIs exist.
  • Dev workflow: Root npm scripts to run API and web together; production build outputs static assets from the frontend.

Product

What it does (directionally)

  • Houses & boards: Track multiple properties in one place with a board layout for side-by-side thinking.
  • Costs & income: Model deposits, mortgage assumptions, utilities, council tax bands, and take-home pay so monthly affordability is visible.
  • Listings & imports: Hooks to pull in listing metadata and media paths where the stack supports it — reducing manual copy-paste.
  • Snapshots: Save point-in-time views when assumptions or listings change, so comparisons stay fair over weeks of searching.

This is a personal tool under active development — not a public service. A polished hosted version may appear later; for now it is a learning project and a practical aid.