Get it running
Requirements, the 10-minute install through the browser assistant, and the one cron job that drives everything else.
Documentation
Everything in one place
The marketing site covers what Wintertrace does and how the pieces fit together. The canonical technical reference for the application itself lives next to the source code on GitHub. This page is the bridge between the two.
Understand the parts
Each major feature has its own page describing what it does, how it fits together, and what assumptions sit underneath.
Run it day to day
Practical context for operators — team setup, shifts, notifications, photos, the things that come up after the first install.
Reference and questions
Common questions, scope of the documentation framing, and where to read what is changing.
Canonical source: GitHub
Wintertrace is open source. The application's README, configuration reference, and release notes live next to the code so they update at the same time as the software itself.
Software README on GitHub ↗
The canonical reference for installation, configuration, and operation of the application itself.
Release notes ↗
Each release lists what changed, what was fixed, and what to watch for when upgrading.
Open issues and discussions ↗
Bug reports, feature requests, and ongoing conversations are public on GitHub.
What this documentation does not pretend to be
Wintertrace documents winter service operations. The documentation on this site explains how the software works — it is not a legal handbook, not a regulatory guide, and not a substitute for advice from a qualified professional.
When a page covers an operator's evidential or compliance needs, it does so descriptively: this is what the software records, this is what the export contains, this is the format the data is in. The legal meaning of that record is for the operator and their advisers to determine.
Still missing something?
If a topic is not covered here or on GitHub, an issue or a quick message is the fastest way to get it added.