What GPStrix connects to today.
This page lists what works now, and marks what is built but not yet switched on. If something you use is not here, ask: some of it is a configuration change, not a project.
Trackers.
Trackers report to the GPStrix tracking gateway, which decodes each tracker's own protocol and hands every position to the platform. There is nothing for you to install or run.
- Hardwired trackers
- Including trackers that read the vehicle's CAN bus: engine RPM, fuel level, coolant temperature, odometer and more. GPStrix knows what each IO element means and shows it by name. Hardware and CAN
- Phones
- GPStrix Field's tracker mode turns an Android phone into a tracker, over the OsmAnd protocol and always over HTTPS. Any other app that speaks OsmAnd can report the same way.
- Other protocols
- The gateway supports far more trackers than the two protocols we have opened. Each protocol listens on its own network port, and the production gateway currently has our standard tracker protocol and the OsmAnd port for phones open. Bringing other hardware means opening its port and testing a unit end to end, which we do with you before you fit a fleet.
Where alerts go.
Every alert lands in the console inbox. A rule can also send it to any of the channels below, each configured once per account. Every send is written to a delivery log, including the ones that failed and why.
| Channel | Status | What you set up | Plan |
|---|---|---|---|
| Working | Your own mail server or any SMTP service: host, port, STARTTLS, sign-in and the from address. | Every plan | |
| Push | Built, not yet live | Nothing on your side. Managers signed in to the GPStrix Fleet app on Android will get push notifications once our notification service is switched on. | Every plan |
| Slack | Working | An incoming-webhook URL from your Slack workspace. Only Slack's own webhook hosts are accepted. | Every plan |
| Telegram | Working | A bot token and the chat ids to send to. | Every plan |
| Webhook | Working | An HTTPS URL of yours. The alert arrives signed, exactly like the event webhooks on the developers page. | With webhooks |
| SMS | Built, needs your template | Your own DLT-registered SMS aggregator: your sender ID, principal entity ID, template code, the aggregator's send URL and its API key. Until your template is registered and approved in the console, the channel refuses every SMS rather than sending it. | Plan feature |
| Built, needs your template | Your own verified WhatsApp Business number: its phone number ID, an access token and your template code. Business-initiated alerts can only use templates WhatsApp has approved, so until yours is approved the channel refuses rather than sends. | Plan feature |
SMS and WhatsApp are separate plan features because every message costs money to send. Email, Slack and Telegram cost nothing per message.
Use your own map provider, and keep its key private.
Out of the box the console uses OpenStreetMap. An account can switch to its own MapTiler, Mapbox, HERE or Google Maps account instead, and the street addresses shown for positions then come from the same provider.
The API key you give us never reaches the browser. Map tiles are fetched through GPStrix, which adds the key on the way, so it cannot be copied out of the page source or a browser's network tab. A tile budget per account stops a runaway screen, or a leaked map session, from spending your provider's monthly quota in an afternoon.
| Provider | Addresses from | Needs your key |
|---|---|---|
| OpenStreetMap | Nominatim | No |
| MapTiler | MapTiler | Yes |
| Mapbox | Mapbox | Yes |
| HERE | HERE | Yes |
| Google Maps | Yes |
OpenStreetMap's free tile servers are meant for light use. A large fleet watching the map all day should use a provider account of its own.
Payments and invoices.
Razorpay takes the subscription payment. The customer authorises a card or UPI mandate once, and each renewal is charged against it. A renewal only counts as paid when Razorpay reports the charge, not when the bank approves the mandate.
Bank transfer or cheque also works. We record the payment against the invoice by hand.
GST invoices are numbered in one unbroken series per financial year, with CGST and SGST or IGST worked out from the place of supply, and sent as a PDF. Your GSTIN goes on the invoice if you give it to us.
Tracking links for people outside the company.
Send a parent, a consignee or a site manager a link to one vehicle. It opens in any browser without an account and shows where the vehicle is now.
A link can expire at a set time or be limited to a delivery window, and you can revoke it whenever you like: a delivery is rescheduled, or the link has been forwarded into a group chat. An expired link, a revoked link and a link that never existed all show the same page, so a stranger guessing links learns nothing.
Your own systems.
An ERP, a dispatch board or a data warehouse can read vehicles, positions, trips, events and reports through the REST API, and receive events as they happen through signed webhooks. Zapier and Make can start a workflow from a GPStrix webhook. Version 1 of the API reads only; it cannot change anything in GPStrix.
Using something we have not listed?
Tell us the tracker model, the system or the channel. We will tell you straight whether it works today, needs setting up, or does not work yet.
Already a customer? Sign in to the console.