TrailSnag.

The comparison

What exists, and where we differ.

You are shopping for a trail tool. Here is the field as we read it — public sources, the date on the page, and for each player what separates us from it. Where another product answers your need better, the card says so too: a comparison that wins on every axis informs nobody.

Field reading of

Read from each vendor’s own public pages. Features and prices change: the date is here so you know what to re-check. We do not publish other people’s prices — they go stale quietly, and their own site is where you should read them.

The field, player by player.

Six products, ordered by how much they overlap with us. Every card leads with what separates us — then, in one line, the need for which you should go to them rather than to us.

TrailsIQ

United States

A trail reporting platform with a free tier. Of everything in this survey, its promise is the closest to ours.

How a visitor reports
Their app, downloaded. Their own reporting page makes “open the app” step 1, with the App Store and Google Play as the only doors — no browser option.
Where the data lives
No mention of data residency anywhere on their site.
Pricing model
Published tiers in US dollars, including a free one.

Where we differ

Reporting happens in the browser, from the sign. Nobody standing in front of a fallen tree with one bar of signal downloads an app — and our data is hosted in Canada, which their site states nowhere.

Where they are the right choice

A free tier that really is one, and anonymity by default — on that half they are as clear as we are.

Trail Sentinel

Québec

Trail maintenance software: assigned tasks, structure inventory and inspection, reports. Mobile and web.

How a visitor reports
Crew-side. Reports come from your members and volunteers, with an account; we found no door for the visitor passing through.
Where the data lives
A local company, but data hosting is stated nowhere on their site. Those are not the same thing.
Pricing model
Published tiers, plus a free community tier for volunteer clubs.

Where we differ

Our reports come from your visitors, not only your crew: everyone walking your network becomes a pair of eyes, with no account and no app to install.

Where they are the right choice

Inspecting structures, assigning work, counting hours. That is their trade; we feed the system you already run instead.

Vélo Québec

Québec

An association, not a piece of software. Annual membership opens access to VQ Gestionnaires — a tool built with Mapgears — to insurance, and to discounts on third-party software in the field.

How a visitor reports
No visitor door. VQ Gestionnaires serves the manager — inspections, incidents, work assignment — and occupies the other end of the chain from our front door.
Where the data lives
Not stated.
Pricing model
Annual membership in Canadian dollars, at two tiers depending on whether the organisation is a non-profit.

Where we differ

We open the door they do not have: the visitor’s. VQ Gestionnaires serves your crew; TrailSnag serves the people walking your network and sends you what they see.

Where they are the right choice

Insurance and a network of managers. The membership is worth what it costs — and it stacks with us.

OuterSpatial

United States

A public-lands and outdoor-community management platform, backed by US agencies.

How a visitor reports
Their app, downloaded.
Where the data lives
United States.
Pricing model
Monthly subscription in US dollars.

Where we differ

The data is hosted in Canada, the interface is in French, and the price is local. For a public body under Law 25 that can settle the question before the feature comparison even starts.

Where they are the right choice

Managing US public lands: their ecosystem is broader than ours, and their references heavier.

Ondago

Québec

A mobile outdoor mapping app, free for organisations that publish their official maps in it.

How a visitor reports
The opposite direction from ours: the manager pushes maps, trail conditions and notifications out to the visitor. We found no door for the visitor to report a problem back.
Where the data lives
A local company; data hosting is not stated.
Pricing model
Not published.

Where we differ

The traffic runs the other way: there the manager broadcasts, here the visitor reports and you receive. They show the way; we tell you what is blocking it.

Where they are the right choice

Publishing a map your visitors consult to find their way. On that ground they already have the audience.

Geotrek

Open source, France

A BSD-licensed open-source suite you host yourself: a public hiking site and a management console.

How a visitor reports
A report form in the browser, on the trail’s own page, landing in the console. Nothing to install — it is the only one in this survey that meets ours on that point, and that deserves saying.
Where the data lives
Wherever you install it. It is your server, and your responsibility.
Pricing model
Free and modifiable; the real cost is hosting and maintaining it.

Where we differ

Nothing to host, nothing to update, and a public map that refuses on its own any stretch leaving the ground you hold. You open the desk, that is all.

Where they are the right choice

Wanting the code in your hands, with the technical crew to host it. Nobody can take it back.

What we found nowhere else

A trail reaches the public map only where somebody answers for the ground — and geometry decides that, never a checkbox.

Everywhere else the path is the same: the organisation buys, its network gets a form. Here the GPS point decides who receives the report, and it is the geometry of verified land — not a checkbox — that authorises publishing.

1/3

Publishing needs someone answerable, proven geometrically

A pin and a stretch reach the public map only where verified land covers them. Correct a boundary inward and whatever sits on ground you no longer hold goes dark on its own, with no action taken on it. That is not a feature: it is a posture about responsibility.

2/3

The data is hosted in Canada

The database sits in Supabase in Montréal (ca-central-1), the API runs on Fly in Toronto. What we will not say is that everything stays in Canada. Our email goes through a US processor, and our Law 25 posture is work in progress — not declared compliance. You can check both halves.

3/3

The visitor installs nothing

A sign, a camera, a browser. The friction is not the account — it is the download: nobody standing in front of a fallen tree with one bar of signal installs an app. It is the only one of our arguments that proves itself in the room, on your phone, in thirty seconds.

What that looks like on a Tuesday morning

A seven-kilometre network with half a kilometre leaving the ground the organisation holds. The platform refuses to publish — not just that half-kilometre, but the whole stretch containing it — rather than draw a public trail across land nobody answers for. Fixing it takes a land decision: get the neighbouring ground, or cut at the property line. Nothing else in this survey would have raised it.

What we do not do.

Three things products on this page do better, and that we will not build. Knowing it before you sign beats discovering it after.

Work-order assignment

We do not assign tasks to a crew and we do not count hours. Every step of a report’s lifecycle goes out instead to the 311 or work-order system you already run, over a signed feed.

Deep structure inspection

Culvert and boardwalk inventories, inspection forms, preventive maintenance, compliance files: that is Trail Sentinel’s trade, they publish it, and it would take a year to catch up.

Consumer mapping

We are not a trail-discovery app. Our public map shows what is reported and what is fixed on land somebody answers for — not a catalogue of hikes to go do.

Did we read your product wrong?

This page is one reading of public pages on one date, done by us, about our competitors. It can age and it can be wrong. If a line is inaccurate, write to us: we will correct it and leave the date in plain sight.