Around 9 PM on a Sunday, our engineering team pushed a button. Two packages went live. One on Google's official Dart package registry at pub.dev, the other on npm. Both shipped with the verified neptrack.com publisher badge attached.
The Flutter SDK had cleared 150 pub points out of 160 on its first scan. We will push that to 160 over the next few releases as we tighten up the documentation comments and a couple of analyser warnings nobody wants to read about. The Node.js SDK shipped with full TypeScript definitions, ESM and CommonJS dual builds, and a clean Socket.IO integration. Apache 2.0 licensed, open source, published officially under the NepTrack organisation.
We have been working towards this moment for a long time.
Why a GPS company in Nepal publishes SDKs in the first place
Most fleet management platforms operating in Nepal today are closed systems. You buy the device, you log in to their dashboard, and the conversation ends there. If you want to integrate your fleet data into your own school management system, your hospital dispatch software, or your logistics ERP, the answer is usually a polite no, or a custom integration quoted three months out at a price that ends the conversation a different way.
We have been getting calls from Nepali software houses and corporate development teams for the better part of a year. They want to embed live vehicle tracking into their own products. They want to send NepTrack data into their accounting tools. They want to build mobile apps for their own fleet customers that talk to NepTrack at the protocol level. Every one of those calls used to end with us writing a custom integration document and walking them through the REST API manually over a Zoom call.
Two SDKs makes that conversation a lot shorter.
This is the first time a Nepali GPS platform has done this
We checked. Every other commercial GPS provider operating in Nepal currently has zero published SDKs on pub.dev or npm. No GitHub organisation, no Apache 2.0 codebase, no verified publisher status anywhere in the public developer ecosystem. The conversation about open APIs in this market has been theoretical for years.
NepTrack is the first commercial GPS platform in Nepal to publish official, open-source SDKs that any developer can install in under two minutes.
That matters less for marketing reasons and more for what it signals to the developer community in Kathmandu, Pokhara, Biratnagar, and everywhere else in Nepal where software gets built. If you are a developer here and you want to integrate fleet tracking into your work, you no longer have to email a vendor and wait for a sales call. You run one command and you are integrated.
What the Flutter SDK does
The Flutter package is published on Google's official Dart package registry as neptrack_core. It is a pure Dart SDK with no Flutter framework dependencies, so it works inside Flutter mobile apps, Dart server processes, and command-line tools alike.
What you get out of the box:
Real-time vehicle position streams over Socket.IO. Full coverage of the NepTrack REST API including vehicles, trip history, fleet reports, alarms, motion logs, geofences, and remote engine commands. Built-in token authentication and automatic retry logic. Typed response models so your IDE catches mistakes before runtime. The package compiles cleanly on every platform the Dart toolchain targets: Android, iOS, Web, and the three desktop platforms.
You install it with one line:
flutter pub add neptrack_coreThe verified pub.dev publisher badge confirms the package is officially maintained by NepTrack. Pub points sit at 150 right now, which is among the higher scores for a freshly published package, and we will push for the full 160 over the next two minor releases.
What the Node.js SDK does
The Node.js package is on npm as @neptrack/core. Built for Node 18 and higher, ships with TypeScript type definitions, supports both ESM imports and CommonJS requires. The Socket.IO integration is the same one the Flutter SDK uses on the wire, so you get consistent real-time behaviour across both runtimes.
Use cases coming in already: Node.js backends behind React and Next.js applications, automation scripts on internal servers, Laravel projects calling NepTrack via a small Node middleware service, webhook handlers pulling fleet data on demand for downstream reporting.
Install:
npm install @neptrack/coreType safety means your IDE shows you exactly what every API method returns. No more guessing at JSON shapes from outdated documentation, no more dropping console.log into the middle of a callback just to figure out the structure of a response.
Apache 2.0 means you can build a business on this
Both packages are licensed under Apache 2.0. That choice was deliberate. We picked it over more restrictive licenses because we want Nepali software houses to be able to embed NepTrack into commercial products without legal friction.
You can fork the SDKs, modify them, ship them inside your own products, charge your customers for the products that use them, and never owe us a royalty. The license requires you to keep the original copyright notice and patent grants in your distribution. That is the only obligation.
If you are a school management software vendor in Nepal who wants to add live bus tracking to your platform, you can integrate NepTrack school bus tracking using the SDK and sell that feature to schools. We benefit because the school becomes a NepTrack customer. You benefit because you ship a feature without spending months building the GPS infrastructure yourself.
Where this fits in NepTrack's developer platform
The SDKs are one piece of a broader developer story we have been building over the last year. The platform now exposes a full REST API with scoped Bearer tokens for authentication, a real-time Data Stream over Socket.IO for live position updates, and an embeddable vehicle widget that drops into any HTML page as a secure iframe. The SDKs sit on top of all of that as the clean, typed clients most developers actually want to use.
The full developer documentation covers every endpoint, the authentication flow, the Data Stream subscription protocol, and how to generate scoped API tokens from the dashboard.
What is coming next
PHP, Python, and Java SDKs are next in the queue. The PHP one is closest because it serves the biggest developer audience in Nepal, and we want it on Packagist within a few weeks. A WordPress plugin is in active development for agencies who want to embed live tracking into client websites without writing code at all. A Postman public workspace is also being prepared so developers can test the API without writing any code first.
If you are a Nepali developer and you have been waiting for the right moment to integrate fleet tracking into something you are building, that moment is now. Install one of the SDKs, hit the API, and let us know what you build.
The team is around if you want to talk about an integration, partnership, or custom build. We are particularly interested in talking to software houses serving schools, hospitals, logistics operators, and government departments. If you have a customer who needs fleet tracking inside your existing product, we want to help you ship it.
