A Laravel API and an Ember console for dispatch and delivery
Fleetbase is an open-source logistics platform that runs on your own servers or as Fleetbase Cloud, hosted by the vendor. It assigns orders to drivers and vehicles and follows each job on a live map until proof of delivery is captured. The API is a Laravel application and the admin console is built with Ember.js. Each module installs into the console as an extension: Fleet-Ops for the fleet and dispatch, Storefront for online ordering, Ledger for invoicing. Other systems connect through the REST API, webhooks or the WebSocket server.
Per-order-type workflows and an open-source driver app
- Workflows defined per order type: each type has its own activity flow, custom fields and automation, and the driver app takes the driver through that flow step by step.
- Navigator, a React Native driver app for iOS and Android. Drivers get orders as they are dispatched, navigate to each stop and record proof of delivery as a photo, signature or scan, while their location streams back to the console.
- An orchestrator for planning runs that allocates vehicles and drivers, assigns orders in batches and schedules routes before they are committed.
- Geofences and telematics: zone events show up as they happen, and GPS devices or sensors can feed the platform.
- A k6 load test attached to every release, comparing latency and error rates with the previous release and checking that one API key flooding the API triggers zero 429 responses for another organization.
Free for in-house fleets, commercial license for resellers
In-house use is free and carries no obligations, according to Fleetbase's licensing page, as long as no outside users reach the instance. A modified version served to outside users has to publish its changes under AGPL-3.0. Keeping them private, selling a logistics SaaS built on Fleetbase or white-labeling it requires the Fleetbase Commercial License.
Aimed at operators who want to own their transport software. The README names haulage firms replacing a legacy TMS, parcel couriers, food delivery and government bodies that want full control of their data. It also points developers at the API as a base for their own logistics products; once such a product is sold as SaaS, the commercial license applies.
MySQL, Redis, a Node.js socket server and 4 GB of RAM at minimum. The repo's docker-compose.yml starts MySQL 8.0, Redis, the SocketCluster real-time server (Node.js), the API with its queue worker and scheduler, and the console. For a single server, the architecture docs ask for at least 4 GB of RAM and 2 vCPUs, recommend 8 GB in production, and require an SMTP server plus FCM or APNs for driver-app push notifications. The standalone binaries attached to each release (Linux, macOS) remove the need to install PHP, but not MySQL or Redis.
Route calculations go to OSRM's public server by default. OSRM_HOST is set to router.project-osrm.org in the compose file and in the docs, which leave self-hosting OSRM as an option.
WebSocket authentication ships switched off. The installer generates the socket key but does not enable authentication, since mobile apps that don't request a socket token yet would be refused. Setting SOCKETCLUSTER_AUTH_ENABLED=true turns it on.
Ten releases in a month, with two modules still at 0.0.x. v0.7.73, published on October 22, 2026, is the tenth since September 23. It patches two critical PHP flaws that let an unauthenticated request run code on the server; its notes tell self-hosted installs to upgrade right away. It ships Fleet-Ops 0.6.74, Storefront 0.4.29, Ledger 0.0.13 and Customer Portal 0.0.16.
The Pallet warehouse module has not shipped yet. It is on the roadmap for October 2026, still marked "in development", yet its only release is v0.0.1 from July 2024 and it is absent from v0.7.73's component list. Navigator v3, the driver app redesign due the same month, is still a draft pull request.