Municipality winter service software
Wintertrace is open-source winter service software that runs on hosting the council controls. No vendor cloud, no licence fee, no per-vehicle pricing. The features map onto how municipal winter service actually works: multi-team shifts, kilometres of priority network, council reporting cycles, audit-friendly records.
Most winter service software is built for the contractor case — a small business with paying customers, a few trucks, and a set of properties under contract. Municipal winter service shares the operational mechanics but differs almost everywhere else: scale, accountability, procurement, data sovereignty.
The features that matter for a contractor still matter for a council — GPS, weather, audit trail. The framing around them changes.
Municipal winter service teams document not just for the property owner — there is no property owner. The audience is internal: the head of works, the council, sometimes the local press, occasionally an audit. Documentation has to hold up under public scrutiny, not just contractual scrutiny.
A council audit can look back five years. The people on the trucks today may not be the people who wrote the records. Structured records survive personnel changes in a way that handwritten notebooks do not.
Most municipal winter service runs as a mix — internal crews on the primary network, contractors on secondary streets or peak demand. The documentation needs to span both without two systems.
Public-sector procurement has its own rhythm. Open-source software with no recurring licence fee tends to be procurement-friendly: no annual sole-source justification, no vendor lock-in risk for the council, no per-vehicle pricing to defend.
Four areas where the standard features stretch to council scale without modification.
Several drivers, several shifts, possibly several depots — Wintertrace handles them as parallel shifts under one installation. The combined record per street or district is one query, not a manual reconciliation across paper logs.
Municipal sites are not five buildings; they are kilometres of roads and dozens of public paths. The customer-and-site model adapts: a municipality models its priority network as customers and individual segments as sites.
Monthly summaries and seasonal aggregations are available out of the box. CSV exports go straight to whatever the council uses for its own reporting. The PDF service proofs make a clean attachment to a council report.
Freedom-of-information-style requests about specific dates and streets can be answered with structured queries and locked records. The audit log shows when each record was created and modified.
Self-hosting is the right shape for public-sector data. The council decides where the data lives.
Hosted on council infrastructure
The application runs on hosting the municipality controls — its own data centre, a public-sector hosting provider, or a regional shared hosting arrangement. The choice is the municipality's.
No data crosses borders without consent
Because there is no vendor cloud in the picture, citizen-adjacent data (location data of public works) does not leave the chosen hosting jurisdiction. Where the data goes is a configuration decision, not a vendor decision.
Source code is auditable
Public-sector procurement increasingly favours auditable software. The Wintertrace source is on GitHub under GNU AGPLv3. An auditor can read the code, run it in a staging environment, and verify what it does.
See also: what self-hosting means here, data protection tools.
Functionally yes — the features (GPS, weather, photos, audit trail, customer portal as "site visibility for residents or contractors") map onto a municipal context. Whether Wintertrace satisfies a specific procurement requirement, a specific national standard, or a specific public-sector framework is for the procuring body to evaluate. Wintertrace does not certify regulatory fit.
Yes. One installation can carry multiple shifts running in parallel, drivers organised into teams, and customers grouped by district. Larger municipalities sometimes prefer one installation per district; the choice is operational, not technical.
On hosting the council controls. The application is PHP and MySQL; any hosting that runs those — internal infrastructure, a public-sector hosting provider, or a regional shared service — works. There is no Wintertrace data centre involved.
Not as a structured offering today. Direct contact with the maintainer is possible; bespoke support, installation help, or development work can be arranged on a case-by-case basis. The core software stays free and open source.
Yes. CSV exports cover most of what council reporting systems need. The underlying MySQL schema is open, so direct integrations are also possible if the IT team prefers them.
Some municipalities expose a public dashboard of which streets have been treated and when. The customer portal can be repurposed for this — operations marked as visible become accessible to defined accounts, including a public-information account if the council wants one. The configuration is the council's responsibility.
Either by running one installation that covers both (with contractors as named drivers or as separate shifts) or by running two installations with their data merged at the reporting layer. Both patterns work; municipalities tend to pick based on contractor count.
Note: Wintertrace provides documentation support for winter service operations. It does not certify fit with any specific public-sector procurement framework, national standard, or regulatory requirement. Whether a Wintertrace deployment satisfies a particular council's obligations is a matter for the council and its legal and technical advisers.
Source code on GitHub. Free under GNU AGPLv3.
Upload one small file to your web hosting, open it in your browser, and the installer puts the latest signed Wintertrace core on your webspace. About ten minutes — no FTP client needed.