Pango
Documentation

Using Pango, and how it works underneath.

The first half of this page is for the people who run buildings. The reference below it is for the people who run the software — and it does not soften anything.

For everyone

Getting going

Pango is one program and one file. There is no account to create, nothing to configure before it will start, and no connection required.

01

Try it with demo data

The fastest way to see whether it fits how you work. Nothing is written to disk.

  1. Download the binary for your machine
  2. Run ./pango --demo
  3. Open localhost:8099
  4. Sign in as demo@pango.local / demopassword
02

Set it up for real

One command, one database file. The first account you create becomes the owner.

  1. Run ./pango --db /var/lib/pango/pango.db
  2. Register the first account — this closes registration
  3. Add your buildings
  4. Create further users as an operator
03

Put it where people work

It binds to your own machine only, until you deliberately say otherwise.

  1. Office machine or NAS: --addr 0.0.0.0:8099
  2. Tablets on the LAN reach it directly
  3. Off-site? See cloud & tunnelled nodes
  4. No network at all? A USB stick is a valid transport
Day to day

The four things you will actually do

Every screenshot here is captured from the compiled binary in demo mode — nothing is mocked up.

The jobs board
Triage the board. Everything outstanding across every building, filtered by unit, priority or who it is assigned to. Drag a job between columns as its state changes.
A job's detail page
Work a job. Add materials and hours as they happen; they add up rather than overwrite. The event thread carries a tenant-visible toggle per entry, so you choose what a tenant would see.
The inspections list
Run an inspection. Schedule an ingoing report at move-in and an outgoing one at move-out. Walk it on a tablet with no signal; it syncs when you are back.
Reports per building and per unit
See where money went. Spend and labour per building and per unit, recomputed from the ledger every time you open it — never from a cached figure.

The full inspections guide →    Every screen, light and dark →

For engineers

Technical reference

These chapters carry honest status markers. Where something is specified but not built, the chapter says so at the top rather than describing it in the present tense.

ArchitectureThe whole system in one binary: layering, the authority model, and why there is no consensus protocol. Sync protocolHLC oplog, stateless symmetric rounds, mutual Ed25519, the merge classes, and the folder transport. ConfigurationEvery flag and environment variable, with defaults and what each one costs you. Self-hostingWhat a deployment is, exposing it safely, backup, multi-site and upgrades. Cloud & tunnelled nodesRunning on a public address: bind, TLS, tunnels, enrolment — and a different threat model. Threat modelWho you are trusting, what the signatures do not do, and the parts that are unflattering.