Open-source logistics and supply chain operating system
Documentation
·
API Reference
·
Try Fleetbase Cloud
·
Book a Demo
·
Discord
Fleetbase is an open-source, modular operating system for logistics and supply chain operations. It covers dispatch, fleet management, live tracking, commerce, warehousing, and finance in one platform, with a REST API, webhooks, and an extension system for everything else. Run it on your own infrastructure or use Fleetbase Cloud.
- Who Uses Fleetbase
- Platform
- Features
- Screenshots
- Apps
- Getting Started
- Releases
- Extensions
- Roadmap
- Documentation
- Community & Support
- Contributing
- Creators
- License
Fleetbase is built for teams that move goods, people, or equipment and want to own the software that runs it. Because every workflow, field, and status is configurable, the same platform adapts to very different operations.
| Industry | How Fleetbase is used |
|---|---|
| Trucking & Haulage | Replace a legacy TMS with real-time tracking, route optimization, and digital proof of delivery. |
| Courier & Parcel | Automate dispatch, raise first-attempt delivery rates, and give customers live parcel tracking. |
| Food & Grocery Delivery | Run on-demand delivery with instant dispatch, live customer tracking, and automated notifications. |
| E‑commerce & Retail | Power same-day and next-day delivery and returns through a headless API. |
| Healthcare & Pharmacy | Track chain of custody and prioritize urgent deliveries with full audit trails. |
| Waste & Recycling | Optimize collection routes, track containers, and produce compliance reports. |
| Container Operations | Follow containers across multi-modal journeys from port to door. |
| Government & Defense | Self-host with role-based access, full audit trails, and complete data sovereignty. |
Developers use Fleetbase as a foundation too, building custom logistics products on its API and extension framework.
Fleetbase is made up of modules that install into the console as extensions. Each one works on its own and integrates with the rest.
| Module | What it does |
|---|---|
| Fleet‑Ops | Fleet management and dispatch: orders, drivers, vehicles, live tracking, route optimization, configurable workflows, and maintenance. |
| Storefront | Headless commerce for on-demand businesses, with multi-vendor marketplaces and native Fleet-Ops delivery. |
| Pallet | Warehouse management for inventory, pick lists, cycle counts, and fulfilment. |
| Ledger | Invoicing, payments, wallets, and accounting for logistics operators. |
| Customer Portal | A self-service workspace for your customers to place and track orders, get quotes and pay, view invoices, manage documents, and open support tickets. |
| AI | Natural-language order creation, operational queries, and order insights powered by OpenAI or Claude. |
| IAM | Identity and access management: users, groups, roles, policies, and two-factor authentication across your organization. |
| Developers | The developer console: API keys, webhooks, socket and system events, and request logs, with separate test and live environments. |
| Navigator App | Open-source driver app for iOS and Android with real-time dispatch, navigation, and proof of delivery. |
| Storefront App | Open-source iOS and Android app for launching your own shop or marketplace. |
| Feature | Description |
|---|---|
| Extensible | Install extensions from the marketplace or build your own to add features directly into the OS. |
| Developer friendly | REST API, WebSockets, and webhooks for integrating external systems or building custom apps. |
| Configurable workflows | Define order types with their own activity flows, custom fields, and automation. |
| Real-time operations | Track drivers, vehicles, and orders live, with geofences and service zones. |
| Telematics | Connect GPS devices and sensors for live feedback from the field. |
| Identity & access | Organizations, users, roles, policies, and two-factor authentication. |
| Dashboards | Build custom dashboards and widgets for visibility into operations. |
| Collaboration | Built-in chat, comments, and notifications across your organization. |
| Internationalized | Translate the console into any language. |
| Self-hosted or cloud | Run it on your own infrastructure with full control of your data, or let us host it. |
Order Board |
Live Operations |
Order Config |
Orchestrator |
Service Zones & Geofences |
Storefront |
Ledger |
Extensions |
Fleetbase has two open-source mobile apps, both built with React Native. They connect to Fleetbase Cloud or to your own self-hosted instance, and you can rebrand them and publish them to the App Store and Google Play under your own name.
|
Navigator is the driver app for Fleet‑Ops. Drivers receive orders as they're dispatched, follow each order's activity flow step by step, navigate to every stop, and capture proof of delivery with photos, signatures or scans. They also report issues, log fuel and chat with dispatch. Their location streams to the console in real time. Navigator v3 is a full redesign, in development in navigator-app#115. The screenshot shows its new Today screen. v3 adds:
|
Storefront is the customer app for the Storefront extension, for iOS, Android and the web. Launch your own shop or service-booking app, or run a multi-vendor marketplace. Customers browse products, check out with the payment gateway you configure, and follow their order live as Fleet‑Ops delivers it. It runs as a single store, a marketplace of stores, or a food-truck network that shows live trucks on a map.
There are three ways to run Fleetbase:
- Fleetbase Cloud: fully managed, with nothing to install. Start a free trial.
- Run locally: self-host with Docker on your own machine or server.
- Deploy in your cloud: run production workloads on AWS, GCP, Azure, or any other provider.
You need Docker with Docker Compose v2, Git, Node.js 18 or newer, and at least 4 GB of RAM allocated to Docker. Then install the Fleetbase CLI and run the interactive installer:
npm install -g @fleetbase/cli
flb install-fleetbaseWhen setup finishes, open the console at http://localhost:4200 and create your first admin account and organization. The API is served at http://localhost:8000.
The running locally guide also covers installing with Docker Compose or the setup script, configuring services like mail, maps, and SMS, and troubleshooting. To work on Fleetbase itself, follow the development setup guide.
Every release publishes Docker images. It also attaches standalone binaries and a performance report to the release, and refreshes the database diagram in this repository.
Each release attaches a single-file build of the Fleetbase API for Linux and macOS:
| Platform | Download |
|---|---|
| Linux (x86_64) | fleetbase-linux-x86_64 |
| macOS (Apple Silicon) | fleetbase-darwin-arm64 |
Each binary is a static FrankenPHP build. It bundles the API, PHP and every PHP extension Fleetbase needs (including GEOS for geospatial queries), along with the web server. You don't need PHP or Composer on the machine. You still need MySQL and Redis, configured through the API's usual environment variables, and the console is served separately. Docker remains the recommended way to run Fleetbase in production.
chmod +x fleetbase-linux-x86_64
./fleetbase-linux-x86_64 php-cli artisan migrate # run Artisan commands
./fleetbase-linux-x86_64 php-server # serve the APIEach release also attaches a performance report: performance-report-<version>.html and .md, with the raw numbers in performance-metrics-<version>.json. Open the latest release to see it.
The report comes from a k6 benchmark (tests/k6/api-release.js) run against a fresh stack booted from source:
- Throughput. Ramping load across the public API: orders, places, contacts, drivers, vehicles, fleets and more. It reports average, p50, p90, p95 and p99 latency, requests per second and error rate overall, for reads and writes, and per endpoint. Every figure is compared with the previous release.
- Rate-limit isolation. One API key floods the API far past its limit while a second organization and the console keep working. The second organization and the console must get zero
429responses.
Release pull requests run the same benchmark as a check. Errors and broken rate-limit isolation always fail it. A latency regression fails it only when it's both large and confirmed by a second run. The benchmark runs on a GitHub-hosted runner, so treat the numbers as a comparison between releases, not a prediction of production throughput.
erd.svg is an entity relationship diagram of the full Fleetbase database: core, Fleet‑Ops, Storefront and the other bundled extensions. A dark version is also available. A workflow regenerates both from the migrations on every release branch and opens a pull request with the update, so the diagram always matches the latest release.
Extensions add features, integrate external systems, or change how Fleetbase behaves. Browse and install them from the console or with the Fleetbase CLI, and publish your own to the marketplace as free or paid extensions.
| Feature | Status | Expected Release | Description |
|---|---|---|---|
| Navigator App v3 | In development | October 2026 | Redesigned driver app: Today view, route manifest, vehicle inspections, offline queue, and inbox |
| Pallet (WMS) | In development | October 2026 | Inventory and warehouse management extension |
| Fleetbase Registry v2 | In development | November 2026 | New extension registry service: one catalog, npm and Composer delivery, licensing, and publisher accounts for cloud and self-hosted instances |
| Dynamic Rules | Planned | 2027 | Rule builder to trigger events, tasks, and jobs |
Want to influence the roadmap? Join the discussion.
- Overview and architecture: how the platform fits together
- Installation: run Fleetbase locally or deploy it in the cloud
- System setup: configure mail, maps, SMS, storage, queues, and sockets
- API reference: endpoints, authentication, and API keys
- Fleetbase CLI: every command for installing, managing, and publishing extensions
- Extension development: build and publish your own extensions
- Database schema: an entity relationship diagram of the full database, regenerated with each release (dark version)
- Discord: Chat with maintainers and other users on Discord.
- Discussions: Ask questions and share ideas in GitHub Discussions.
- Bugs: Search the issue tracker first, then open a new issue.
- Security: Report vulnerabilities privately as described in SECURITY.md.
- Support plans: See community, cloud, and enterprise support options.
- Releases: Read changelogs on the Releases page and announcements on the Fleetbase blog.
- X: Follow @fleetbase_io.
We welcome contributions from the community.
- Report bugs: Open an issue
- Suggest features: Start a discussion
- Submit pull requests: Read the Contributing Guide and the Code of Conduct
- Translate: Add or improve a language by following TRANSLATING.md
- Write documentation: Help improve the docs
- Build extensions: Create and share extensions
To set up a local development environment, see the development setup guide.
Fleetbase is dual-licensed. Choose the license that fits how you use it.
Open source (AGPL-3.0). Fleetbase is released under the GNU Affero General Public License v3.0. You can use, modify, and self-host it freely, including to run your own commercial operations. If you modify Fleetbase and make it available to others over a network, you must release those modifications under AGPL-3.0.
Fleetbase Commercial License (FCL). The commercial license removes the AGPL-3.0 obligations. It lets you keep modifications proprietary, build SaaS products on Fleetbase, and white-label or distribute it under your own brand. It also includes support options and IP indemnification.
Read the licensing overview to see which license applies to you, or see the Commercial License for details. Questions go to hello@fleetbase.io.
Copyright © 2026 Fleetbase Pte. Ltd. All rights reserved.