Publications
2026, in review.
A year of shipping, breaking, and fixing things in the open. Here's what actually happened, not just the parts that went well.
Highlights
Three things worth calling out.
The full write-ups are linked from each post — this is the short version.
01
◈
Tideline went offline-first
The biggest architecture change of the year — councils with patchy internet during a storm now have the whole map cached locally.
- Full offline map cache shipped in v4
- Deployed to 5 new coastal councils
- 72-hour surge forecasting added
02
◑
Coldwatch crossed five countries
Sensor cost came down, deployment count went up. The SMS-only approach kept working exactly as intended.
- Sensor cost dropped under $9
- Now live in five countries
- Alert latency down to under 3 minutes
03
◫
Commons hit 60 organisations
What started as an internal tool for our own field partners became the thing small NGOs actually asked for by name.
- 60+ organisations hosted
- Zero paid tiers added — still free, still exportable
- Full data export shipped for every org
By the numbers
- Products shipped or updated
- 4
- New contributors
- 11
- Posts & write-ups published
- 19
- Countries with an active deployment
- 9
- Lines of code merged
- 48,000+
What we got wrong
Tideline's first offline cache implementation silently dropped gauge updates older than 24 hours — a council found it during a real storm, not a test. Fixed in v4.0.2, and it's now part of the release checklist for every product.
Help write 2027's review.
Every entry in next year's review starts as a pull request, a bug report, or a write-up someone decided to publish.