Iron Route GPS: Built by Truckers, Hosted in the USA
Iron Route GPS: Built by Truckers, Hosted in the USA
Two things shape every product. Who wrote the spec, and where the data lives.
For most truck-navigation apps, the spec is written by a product manager who has never held a CDL, and the data lives across half a dozen countries because the cloud team optimized for compute price, not for sovereignty. That sounds like a small thing. It is not.
This is what changed when a CDL driver wrote the spec for Iron Route GPS.
What a CDL spec actually says
If you have run a 70-hour 8-day clock, you know that the difference between a tool that helps and a tool that gets in the way is state preservation. State means: if I am two-thirds of the way through a route, get a roadside random, eat lunch, and come back to the cab — the app remembers. Not just my route. My favorite fuel stop on this lane. My weigh-station bypass status from PrePass. My split-sleeper plan. My DOT 11/14 timer. The next legal place to park.
Almost no truck nav app preserves state across all of that, because the engineer writing it has never had a dispatcher call them at 04:30 asking why the app forgot the route.
So the Iron Route spec begins with this rule: everything is state-aware, nothing is reset.
It reads like this:
- The app boots into the last route, last screen, last voice mode.
- The voice command "next fuel" looks up YOUR fuel preferences, not a generic Pilot list.
- The "I'm shutting down for the night" command parks the truck, logs the location for tomorrow's start, and sets your alarm based on remaining HOS.
- The "find me legal parking" command excludes locations where you have been turned away before.
These are the things a driver puts on the spec when the driver writes the spec. They are not the things a product manager puts on the roadmap when the roadmap is built around DAU/MAU charts.
Where the data lives
We made the unfashionable choice to host on US infrastructure (HostGator, with a planned move to a HostGator NVMe VPS in Virginia for heavy compute and AI). It is unfashionable because every cool kid in software now hosts on Cloudflare R2, AWS Mumbai, and a Cloudflare Worker that fans out to twenty edge regions including Singapore and Frankfurt.
That is wonderful for latency. It is awful for sovereignty.
If you are a US owner-operator, your routes, your fuel patterns, your home address, your customer pickup-delivery cadence, and your behavioral fingerprint are commercial intelligence. They are intelligence about you, your customers, and the lanes you compete on. Hosting that data through an off-shore CDN that sells aggregated traffic intelligence to anyone with a credit card is, at minimum, a poor security posture. At worst, it is feeding the lane-rate compression that crushed margins from 2018 to 2025.
We chose: only US-domiciled infrastructure. Period. No off-shore replication. No cross-border CDN. Latency suffers a tiny bit. Sovereignty wins everything.
What this looks like in production
We pay attention to four things every release:
1. Routing accuracy on truck-legal restrictions. Height, weight, hazmat, length, bridge clearances, residential restrictions. We benchmark every release against 30 hand-curated routes pulled from real driver runs. The day the benchmark drops, the release does not ship. 2. Voice nav latency under poor signal. A voice command in a deadband (West Texas, central Wyoming, the Allegheny tunnels) cannot fail. We pre-cache the entire route's voice graph to local storage. The voice still works at 0 bars. 3. Offline maps. US + Canada + Mexico tile pyramids, vector + raster, downloadable per-state. Offline IS the default mode for long lanes. 4. Battery use. A truck nav app that drains a phone in 4 hours is unusable. We benchmark battery use per 100 miles and refuse to ship a release that regresses by more than 8%.
That is what a driver-written spec looks like in code review.
Why it matters
Trucking is one of the few industries left where the operator is also the entrepreneur. An owner-operator buys his own truck, signs his own loans, eats his own fuel. Every dollar that leaks out to a $90/month subscription, a 14% factoring fee, or a 25% broker spread is a dollar that does not compound into the next truck.
We think the right place for software in trucking is as cheap and useful as possible, not as expensive and locked-in as the market will tolerate. We are pricing accordingly: free tier with no daily cap, $4.99/mo Pro, $9.99/mo Fleet, no per-driver upcharge.
If you have run trucks for more than a year, you can recognize a tool built by someone who has been there. Try Iron Route at sultanfreight.com/iron-route/. The free tier is forever-free. The Pro tier costs less than a single fuel stop's coffee tab.
— Ramses Lara, founder, TruckerProfit Inc., a Sultan Freight Logistics company