# What's in the High Point GPS Add-On Library?

The High Point GPS add-on library is where most of the platform's flexibility lives. Here's what kinds of Add-Ins are in it, and how to evaluate one.

Source: https://www.highpointgps.com/resources/add-on-library-guide
By Israel Margulies, CEO & Founder — published 2026-08-11, updated 2026-09-19

## What the Add-On Library Actually Is

The High Point GPS add-on library is a catalog of Add-Ins and Add-Ons, built both by the platform's own developers and by third parties, that extend what the High Point GPS platform can do beyond its core reporting and tracking features. It exists because the platform is built on a public SDK and open data architecture, so outside developers, including resellers like High Point GPS, can build real functionality on top of the platform instead of waiting for the platform to build every feature in-house.

That openness is the whole point. A closed telematics platform limits you to whatever the vendor decides to build. An open one, with an active add-on library behind it, means the feature you need has a real chance of already existing, or of being buildable by whoever supports your account.

It's worth noting that not every telematics vendor takes this approach. Some competitors run a fully closed platform where every feature ships from the vendor directly, on the vendor's own timeline. That can feel simpler on day one, but it also means you're stuck waiting if a feature you need isn't already on their roadmap.

## The Kinds of Add-Ins You'll Find

Add-on library listings generally fall into a handful of recurring categories: safety and video (dash cam and event-review tools), compliance (state- or province-specific reporting helpers, inspection tools), fuel card integrations, dispatch and routing connectors, maintenance and diagnostics add-ons, and asset-tracking extensions. Some are built by the platform's own team and maintained as part of the core ecosystem; many others are built by third-party companies or, like our own GeoDocs, by resellers solving a specific customer problem.

Fuel card integrations are a good example of why this matters in practice. Reconciling fuel purchases against GPS-verified trip data by hand is exactly the kind of tedious cross-referencing an Add-In can automate, catching a fuel card used somewhere the tracked vehicle never actually went, a common fraud pattern that's otherwise hard to catch without manually comparing two separate systems.

![Diagram of telematics data flowing from the vehicle to the GPS tracking device, the cloud, the High Point GPS platform and the fleet's own systems](https://www.highpointgps.com/images/figures/telematics-data-flow.webp)

*Where the data goes: the engine bus and sensors feed the GPS tracking device, the cloud applies the fleet's rules, and the High Point GPS platform or the API hands it to your systems.*

## Built-In vs. Add-On Library vs. Custom

It's worth keeping three tiers straight. Core High Point GPS platform features (tracking, basic reporting, driver scoring) come with the platform regardless of Add-Ins. Add-on library Add-Ins are pre-built extensions you install to add a specific capability, some free, some paid, built by the platform or a third party. Custom Add-Ins are built specifically for one fleet's workflow, either in-house by a technical team or, more commonly for a fleet without in-house developers, by a fleet tracking provider like High Point GPS.

Our own Add-Ons library brings these together in one place: the add-on library hardware and software we've vetted, alongside custom Add-Ins we've built ourselves that don't exist anywhere else, like GeoDocs for document management in the cab.

Knowing which tier a given feature request falls into changes the conversation. "Is there an add-on library Add-In for this" is a quick search. "Can this be built" is a different, longer conversation with your reseller about scope, timeline, and cost, but it's a conversation that's actually possible on an open platform in a way it simply isn't on a closed one.

## How to Evaluate an Add-On Library Add-In Before Installing

Before installing anything, it's worth checking a few things directly: what data or system access the Add-In actually requests, whether it's been updated recently (an abandoned Add-In is a real risk on a platform that keeps evolving), and who actually supports it if something breaks, the original developer, the platform, or your reseller. That last point varies a lot between listings and matters more than most buyers expect until they need support and don't know who to call.

It's also worth testing an Add-In on a small subset of vehicles before rolling it out fleet-wide, the same way you'd pilot any new software. An Add-In that behaves well on five vehicles usually scales fine to five hundred, but catching an unexpected data conflict or performance issue on a small pilot group is a lot less disruptive than discovering it after a full rollout.

## When to Ask for a Custom Add-In Instead

If you've looked through the add-on library and nothing quite fits how your team actually works, that's usually the point to ask your reseller about a custom Add-In rather than settling for a close-enough fit or building a manual workaround. This is exactly the kind of gap the platform's open SDK was built to let resellers fill, and it's a meaningfully different conversation than "does the platform have a feature for this," since the honest answer is often "not yet, but it can be built."

GeoDocs is a real example of this playing out: High Point GPS built it because document management in the cab wasn't a solved problem in the add-on library at the time, not because we set out to build software for its own sake. That's usually the actual trigger for a good custom Add-In, a specific, recurring workflow pain that off-the-shelf tools keep almost, but not quite, solving.

## Add-On Library Add-Ins High Point GPS Installs Most

A short list from the catalogue, by the problem each one answers, as a starting point for a fleet browsing for the first time.

| Problem | Add-In or Add-On | Type |
| --- | --- | --- |
| Documents expire in gloveboxes | GeoDocs | Custom Add-In by High Point GPS |
| Nobody reviews HOS violations | HOS Driver Summary | Add-In, scheduled report |
| Dispatch assigns loads without seeing hours | Compliance Data Summary | Add-In on the live map |
| Driver profiles fail roadside data checks | ELD Settings Validator | Add-In |
| Cross-border drivers on the wrong ruleset | Ruleset Switcher | Add-In in the driver app |
| Fuel card misuse | BlueArrow Fuel | Add-In with fuel card integration |
| A customer asks where the truck is | Timeline Map; Public Tracking Portal | Add-In; custom web app on the API |
| Who was driving the shared truck | IOX-NFCREADERA driver ID | Add-On |
| Video for claims and coaching | Dual Dash AI Camera, Lytx Surfsight, Rosco DV6 | Add-On cameras |
| Temperature record per compartment | Bluetooth pucks, wired probes and a sensor gateway | Add-On sensors |

## FAQ

### Is everything in the High Point GPS add-on library free?

No. Some Add-Ins are free, others require a paid subscription or one-time purchase, and pricing varies by developer. It's worth checking the specific listing rather than assuming either way.

### Who supports an add-on library Add-In if something goes wrong?

It depends on the specific Add-In. Support can come from the original third-party developer, from the platform directly for its own listings, or from your reseller if they helped implement it. Confirm this before relying on an Add-In for something business-critical.

### Can High Point GPS build a custom Add-In that isn't in the add-on library?

Yes. That's exactly what we've done with tools like GeoDocs, built for a specific workflow the add-on library didn't already cover. If nothing existing fits your team's process, a custom Add-In is worth asking about.

### Should I pilot a new Add-In before rolling it out fleet-wide?

Yes, it's good practice. Testing on a small group of vehicles first surfaces data conflicts or performance issues while they're still easy to fix, rather than after a full rollout has already made the same issue harder to unwind.

## Sources

- [Platform documentation](https://www.geotab.com/)