After looking at SketchForge, House Planner is a natural next stop.

Both are browser-based design tools. But they are not solving the same problem.

SketchForge is about making 3D parts. House Planner is about planning a whole private house: walls, rooms, plot, utilities, underfloor heating, map alignment, estimates, versions, and snapshots.

That makes it much closer to:

self-hosted construction planning

than generic browser CAD.

What is House Planner?

House Planner is an MIT-licensed self-hosted house planning app.

It gives you:

  • a true-scale 2D floor plan editor in millimetres;
  • a 3D preview;
  • satellite map overlay and GeoJSON parcel support;
  • wall, opening, furniture, material, and room data;
  • sewer, electrical, water, and hydronic underfloor-heating layers;
  • calculations and warnings for those utility networks;
  • a priced bill of materials from a JSON catalog;
  • server-side plan versions and named snapshots;
  • one-password login;
  • no database requirement.

The repo describes the stack as React + PHP with no database. The plan lives as JSON files on your own server.

Why It Is Different from SketchForge

SketchForge and House Planner are both useful for homelab/makerspace-style design work, but the mental model is different.

Question House Planner SketchForge
Main object A full house/site plan A 3D part/model
Primary workflow Draw walls, rooms, networks, estimate materials Create primitives, cut holes, export model files
Main storage Server-side JSON with revisions/snapshots Browser-local storage plus optional shared .skf shelf
Backend PHP files plus file storage Next.js server for app/shared projects
Database None None
Best fit Construction planning, BOM, utility layout Printable parts and quick 3D object design
Offline behavior Needs its PHP server, but can run on LAN without internet More browser-local for private projects

So the quick distinction:

SketchForge = browser CAD for objects
House Planner = self-hosted planner for a house project

Architecture Overview

House Planner is refreshingly simple:

React/Vite frontend -> PHP API -> JSON files on disk

Observed stack:

Layer House Planner Uses
Frontend React 19, TypeScript, Vite
State Zustand + zundo
2D editor Konva / react-konva
3D preview three.js, React Three Fiber, drei
Geometry clipper2, three-bvh-csg
Map MapLibre GL, proj4
Validation zod
Backend PHP 8.1+ API
Storage JSON files, versions, snapshots
Docker runtime PHP 8.3 Apache image
License MIT

There is no Postgres, Redis, queue, SQLite, or object storage layer.

The Dockerfile builds the Vite app with Node 22, copies the result into a PHP/Apache image, and persists the planner storage under:

/var/lib/house-planner

Self-Hosting House Planner with Docker

I added a Home-Lab compose:

Start it with:

cd /home/jalcocert/Desktop/Home-Lab/house-planner
docker compose up -d --build

Then open:

http://localhost:3817/
http://192.168.1.2:3817/

First-run setup is at:

http://192.168.1.2:3817/api/setup.php

That setup page lets you choose storage and set the one installation password.

Until setup is completed, the main editor can load but it will show a server connection error. That is because /api/plan.php returns:

HTTP 503 not_installed

That state means the app is reachable but no password/config has been created yet.

Field Note: Docker Trial

I built and ran the Docker image locally from commit:

5c91280da6c5cc84c1a534ef80ddafb64a6b5baa

The test command:

docker build -t house-planner:foss-trial .
docker run -d --name house-planner-foss-trial --restart unless-stopped \
  -p 3817:8080 \
  -e HOUSE_STORAGE=/var/lib/house-planner \
  -v house-planner-foss-trial-data:/var/lib/house-planner \
  house-planner:foss-trial

Result:

container: house-planner-foss-trial
status: healthy
URL: http://127.0.0.1:3817/
LAN URL: http://192.168.1.2:3817/
setup wizard: http://192.168.1.2:3817/api/setup.php
/api/plan.php before setup: 503 not_installed
image size: about 514 MB

I intentionally left the trial in first-run setup mode so you can choose the password from the browser.

How Storage Works

This is the most important practical difference from SketchForge.

House Planner stores the plan on the server.

The storage folder contains:

Path Purpose
config.php Password hash, cookie token, settings
current.json Current plan
versions/ Every saved revision
versions.jsonl Revision index
snapshots/ Named restore points
snapshots.jsonl Snapshot index
site-fixed.json Optional locked parcel/site data

In Docker, all of that lives in the house-data volume.

Backups are therefore straightforward:

back up the whole storage folder or house-data volume

Do not run docker compose down -v unless you intentionally want to delete the plan history.

Editing Through JSON and AI Assistants

One detail I like: the plan is a strict JSON document.

That means the browser is not the only editing surface. The repo includes scripts to pull, validate, and push the plan:

scripts/plan-pull.sh
node scripts/plan-validate.mts plans/server.json
scripts/plan-push.sh

The same versioned API is used by both the browser and scripts. If the plan changed on the server, the push exits with a conflict instead of overwriting silently.

That makes House Planner unusually friendly to assistant-driven workflows:

pull JSON -> ask an assistant to add/move/change geometry -> validate -> push as a new version

For construction planning, that is much more useful than a closed binary file.

FAQ

Conclusion

House Planner is much more specialized than SketchForge, and that is a strength.

If you want a quick browser CAD tool for parts, use SketchForge.

If you want a self-hosted planning surface for an actual house project, House Planner is the more relevant project: true-scale plan, 3D preview, site map, utility layers, estimates, JSON versions, and no database.

For a homelab, the architecture is easy to reason about:

Docker container + PHP API + JSON storage volume

That is a good shape for a personal construction-planning tool.