FleetBase

Modular, developer-first logistics infrastructure — honestly reviewed. All sources evaluated, including their origin.

TL;DR

• What it is: Open-source (AGPL-3.0) modular logistics operating system — order dispatch, real-time fleet tracking, driver mobile app, and customer ordering, all in one self-hostable stack [README][homepage].
• Who it’s for: Courier companies, food delivery operators, field service teams, and logistics SaaS developers who need infrastructure they own rather than yet another per-driver, per-task SaaS bill [README].
• Cost savings: Onfleet starts at $550/month for 2,000 tasks. Track-POD runs $29–99/month per driver. FleetBase self-hosted is software-free — infrastructure runs under $50/month regardless of order volume. At 20 drivers, that’s $10,000+/year saved versus premium logistics SaaS [homepage].
• Key strength: Genuinely modular — deploy only FleetOps for dispatch, add Storefront for customer ordering, layer in Pallet for inventory. Each extension installs independently. The developer toolkit (SDK, CLI, WebSockets, REST API) is real and well-documented [README][3].
• Key weakness: AGPL-3.0 license is a hard constraint for commercial embedding — modify and run it as a service, and you must open-source your changes. Cloud pricing is not publicly listed. Independent third-party reviews are sparse, which is itself a signal [README].

---

What is FleetBase

FleetBase describes itself as a “modular logistics and supply chain operating system” [README]. The honest translation: it’s a self-hostable backend for running delivery and fleet operations, with a dashboard, a driver mobile app, an order management system, and a set of extensions you install based on what your operation actually needs.

The company — Fleetbase Pte Ltd — is Singapore-based and has been operating since 2018 [4]. Co-founder Shiv Thakker has presented at LogTech Asia and GreenFreight Asia [2][4]. The website claims 6,000+ active users and 10+ enterprise customers [homepage], numbers that come from the company itself and can’t be independently verified. GitHub shows 1,787 stars and an AGPL-3.0 license [merged profile].

That star count is worth holding in mind. For context, n8n (workflow automation) sits at 100K+ stars, Activepieces at 21K. FleetBase’s 1,787 reflects the narrower niche — logistics infrastructure doesn’t go viral on Hacker News — but it also reflects where this project is in its community lifecycle.

The core modules FleetBase ships:

• FleetOps: the main TMS — dispatch, route planning, live fleet map, Kanban order board, service zones [homepage]
• Storefront: headless commerce for on-demand ordering, multi-vendor support, location-aware menus, customer ordering flow [3]
• Navigator: native driver mobile app — receives orders, tracks routes, captures proof of delivery, syncs in real-time [3]
• Customer Portal: live order tracking and delivery updates for end-customers [homepage]
• Pallet: inventory and warehouse management — SKU tracking, inward/outward stock, fulfillment integration [homepage]
• Developer Console: CLI, SDKs, API key management, log viewers, webhooks [homepage]

---

Why people choose it

There’s a problem writing this section honestly: the sources available for this review are primarily the company’s own blog posts, product pages, and website copy [1][2][3][4][5]. There are no Trustpilot threads, no G2 comparison pages, no r/selfhosted migration stories. Independent community reviews of FleetBase don’t exist at meaningful scale yet. That absence is itself a data point.

What the company’s materials and architecture do reveal:

The target customer is not a solo founder clipping Zapier costs. Shiv Thakker’s presentations at LogTech Asia [4] and GreenFreight Asia [2] are pitched at logistics technology professionals thinking about digital transformation — operators with real fleets and real operational complexity. The product assumes organizational scale: multiple drivers, multiple order types, custom workflows.

The developer-first positioning is genuine. The CLI (npm install -g @fleetbase/cli, then flb install-fleetbase) [README], the JavaScript SDK, real-time WebSocket subscriptions for order and driver events, service quotes API, driver proximity search — these aren’t checkbox features. They’re building blocks for engineering teams that want to build on top of logistics primitives rather than navigate a vendor dashboard [homepage].

The on-demand delivery use case is the clearest product fit. Storefront is built specifically for what the company calls “hyperlocal commerce” — a food delivery operator, a multi-vendor marketplace, a grocery-on-demand app [3]. The white-label driver app (Navigator) can be published under your own App Store accounts. For a startup building this kind of product from scratch, the SaaS alternative is Shopify + Onfleet + a custom mobile app — easily $2,000+/month combined, before you’ve customized anything.

Where the pitch is thinner: the blog posts lean toward thought leadership [4][5] and sustainability positioning [2] rather than product benchmarks or customer migration stories. The microservices architecture post [5] explains why microservices are good in general — not what makes FleetBase’s implementation specifically better than alternatives. That pattern is what you see from a company building market awareness, not one with a documented body of production deployments.

---

Features

Order and dispatch:

• Kanban board for visual order management [README]
• Custom order workflow configuration — define logic, rules, automation, activity flows, and custom fields per order type [README]
• Real-time order tracking on interactive map [README]
• Service zones — define geographic service areas for fleet assignment [homepage]
• Support for first-mile and last-mile operations within a single system [homepage]

Fleet tracking:

• Live fleet map with all drivers and active orders visible simultaneously [README]
• Real-time driver location updates via WebSocket [homepage]
• Driver proximity search by radius via API [homepage]
• Service quote fetching for pickup/dropoff pairs in real-time [homepage]

Mobile (Navigator driver app):

• Order receipt and turn-by-turn route display [3]
• Status updates and proof-of-delivery photo capture [3]
• Issue reporting synced back to the dispatch dashboard [3]
• Open-source and forkable — publish under your own App Store accounts [3]

Developer platform:

• REST API with standard endpoints for orders, drivers, quotes, tracking [homepage]
• JavaScript/TypeScript SDK (@fleetbase/sdk) [homepage]
• WebSocket subscriptions for real-time events [homepage]
• Webhooks for automation triggers [README]
• CLI for install and management [README]
• Log viewers and API key management built into the dashboard [homepage]

Storefront (on-demand commerce):

• Multi-vendor product catalog with real-time search [3]
• Customer ordering flow with delivery map [3]
• Location-based menus for mobile vendors (e.g., food trucks with rotating locations) [3]
• Multi-currency and multi-language support [3]
• White-label mobile ordering app, publishable to app stores [3]

Extension marketplace:

• Extensions install as new modules into the FleetBase dashboard [homepage]
• Publish private extensions for internal use or list publicly [homepage]
• flespi GPS device management integration exists as an available extension [4]
• Architecture supports third-party and community-built extensions [homepage]

---

Pricing: SaaS vs self-hosted math

FleetBase Cloud: Pricing is not publicly listed. The website presents “Start Free Trial / Self Host / Deploy On AWS / Talk to an Expert” with a 7-day trial requiring no credit card [homepage]. There is no published tier breakdown, no per-driver or per-order pricing table. Actual numbers require a sales conversation. This is the enterprise model — not inherently a problem, but it prevents self-service cost evaluation.

FleetBase self-hosted:

• Software license: $0 (AGPL-3.0) [README]
• VPS: $20–50/month for a production-ready server (4–8GB RAM minimum for real fleet load)
• S3-compatible storage: variable, based on proof-of-delivery photo volume

Competitor pricing for comparison:

Tool	Model	Cost
Onfleet	SaaS, per task	$550/month (2,000 tasks)
Tookan	SaaS, per task	$35–89/month with task caps
Track-POD	SaaS, per driver/month	$29–99/month per driver
Route4Me	SaaS, per driver/month	$200+/month for small teams
FleetBase Cloud	Enterprise, contact sales	Not public
FleetBase self-hosted	AGPL-3.0, run your own infra	~$20–50/month in VPS only

The math at 20 drivers on Track-POD Professional (~$49/driver/month) is $980/month. Self-hosting FleetBase on a $40/month server handles the same 20 drivers for $40/month in infrastructure. Over 12 months, that’s roughly $11,000 back. The caveat: Onfleet and Track-POD include SLA-backed uptime, support, and continuous platform updates. Self-hosting means you own the incidents.

---

Deployment reality check

Three install paths exist [README][homepage]:

1. CLI quickstart: npm install -g @fleetbase/cli → flb install-fleetbase — wraps Docker Compose, fastest path for getting something running
2. Docker Compose: manual configuration for more control over database, storage, and service tuning
3. AWS deployment: listed as a first-class option with a dedicated CTA on the homepage [homepage]

What production self-hosting actually requires:

• Linux VPS with 4–8GB RAM (underpowered hardware will struggle under real order volume)
• Docker and docker-compose
• Domain and SSL via Caddy or nginx reverse proxy
• PostgreSQL and Redis (bundled in default compose, or externalized)
• SMTP provider for notifications and user invites
• S3-compatible object storage for driver proof-of-delivery photos — this adds up in high-volume operations

The AGPL-3.0 detail that changes the calculation: AGPL-3.0 requires that if you run a modified version of FleetBase as a network service — including as a SaaS product you sell to others — you must release your modifications under the same license. If you’re a logistics software company building a proprietary platform on top of FleetBase, you need either a commercial license agreement with Fleetbase Pte Ltd or you open-source your product. This is not MIT. Internal operational use is unaffected — an operator running FleetBase for their own courier fleet has no obligation.

What can go sideways:

• Community size is thin. 800+ community members [homepage] for a platform covering dispatch, inventory, commerce, and mobile apps is a small support network. When something breaks, Discord is your first line of help — which matters more at 2am on a high-volume delivery day than it does during evaluation.
• The extension marketplace exists conceptually but the catalog appears early. Most integrations will go through the REST API rather than pre-built marketplace extensions.
• Forking the Navigator driver app means owning App Store submissions, iOS developer account fees, and mobile app review cycles — real overhead that closed-source platforms absorb for you [3].
• GitHub star count (1,787) versus platform ambition suggests limited battle-testing in the wild compared to more established tools.

Realistic setup time for a technical team: 1–2 days to production (domain, SSL, email, workflow configuration). For a non-technical operator with a developer helping: 3–5 days including driver app setup and order workflow customization.

---

Pros and cons

Pros

• Genuinely modular. Install FleetOps without Storefront. Add Pallet later when inventory matters. Each module is independent — you’re not paying for features your operation doesn’t use [README][homepage].
• Real developer tooling. SDK, CLI, REST API, WebSockets, webhooks — this is built for engineering teams, not click-through admins. The service quotes API and real-time driver proximity search are useful logistics primitives, not just dashboard wrappers [homepage].
• White-label driver app. Navigator is open source. Publish it under your own brand on iOS and Android without paying per-driver app licensing fees — a concrete advantage over commercial platforms that charge for this [3].
• On-demand commerce stack in one platform. Storefront + FleetOps + Navigator covers what a food delivery or hyperlocal commerce startup would otherwise stitch together from three separate vendors [3].
• No per-task or per-driver ceiling on self-hosted. Your VPS cost stays flat whether you dispatch 10 orders or 10,000.
• Company operating since 2018 [4] — this isn’t a weekend side project with no commercial backing. There’s business momentum behind the platform even if the public community is still small.

Cons

• AGPL-3.0 limits commercial embedding. Modify and run it as a service, open-source your changes or negotiate a commercial license. For operators using it internally, not a concern. For software companies building products on top of it, this is a gating issue [README].
• Cloud pricing not public. No tiers, no per-driver numbers, no self-serve cost estimate. You have to talk to sales to know what the managed option costs [homepage].
• Sparse independent reviews. All sources for this review are company-produced content. There’s no equivalent of a Trustpilot corpus, G2 comparisons, or Reddit migration threads to triangulate against. You’re evaluating based on company materials and the codebase itself.
• Small community. 800+ community members and 1,787 GitHub stars for a platform this complex is a thin support network for a mission-critical operations tool.
• Extension marketplace is early. The architecture is solid; the catalog of available extensions is thin. Expect to build most integrations via the API rather than installing from the marketplace.
• Mobile app ownership adds overhead. Forking Navigator means owning the full iOS and Android release pipeline — App Store fees, review cycles, code signing [3].
• No public roadmap found in available materials — hard to assess what feature velocity looks like or what’s planned for the next 12 months.

---

Who should use this / who shouldn’t

Use FleetBase if:

• You’re running a courier, food delivery, or field service operation with 10+ drivers and your current SaaS bill exceeds $400–500/month. The infrastructure math is obvious [homepage].
• You’re a development team building a logistics SaaS or on-demand commerce platform and want an open-source backend to extend — and you’re either comfortable with AGPL or negotiating a commercial license [README].
• You need a white-label driver app publishable under your own brand without per-driver licensing overhead [3].
• You’re building a hyperlocal delivery or on-demand ordering product and want integrated ordering + dispatch in one stack rather than three vendor relationships [3].
• You have at least one engineer comfortable with Docker, Linux server administration, and reading GitHub issues when something goes wrong.

Skip it (look at Onfleet or Track-POD) if:

• You need SLA-backed uptime, dedicated support, and continuous updates — and the monthly bill is a manageable cost of doing business.
• You have fewer than 5–8 drivers and the self-hosting overhead doesn’t justify the savings.
• Your operation needs standard workflows that off-the-shelf SaaS covers without customization.

Evaluate the AGPL carefully before proceeding if:

• You’re a software company building a commercial logistics product. AGPL-3.0 requires releasing your modifications. Get a lawyer or a commercial license agreement with Fleetbase Pte Ltd before you start building [README].

Consider waiting if:

• You need a mature community and documented production deployments before betting mission-critical operations on a platform. Give it another 12–18 months if community size is a genuine risk threshold.

---

Alternatives worth considering

• Onfleet — the benchmark commercial fleet management SaaS. Best-in-class for UX and driver communication, expensive at scale ($550/month for 2,000 tasks). No self-hosting option. Appropriate when you need proven support and don’t want to manage infrastructure.
• Tookan (JungleWorks) — cheaper SaaS fleet dispatch, starting at $35/month. More accessible for small operations; per-task limits become a constraint at volume. Closed-source, no self-hosting.
• Track-POD — per-driver SaaS ($29–99/driver/month) with strong proof-of-delivery features. Good fit for smaller fleets on a budget; not self-hostable.
• OptimoRoute — focused narrowly on route optimization and scheduling. Less full-featured than FleetBase but better at the specific problem of multi-stop route planning for larger fleets.
• Coopcycle — open-source (CoopCycle proprietary license) platform built specifically for courier cooperatives. Narrower scope, smaller feature set, but well-deployed in European cooperative networks and has an active community.
• Custom build on open mapping infrastructure — for engineering teams with capacity, building on OpenStreetMap + a custom dispatch layer + a generic mobile framework avoids all license constraints, but the build cost is six months minimum.

For a logistics operation that’s outgrown SaaS pricing and has engineering capacity, the realistic shortlist is FleetBase vs. Coopcycle vs. building in-house. FleetBase is the most feature-complete option in that group; Coopcycle is narrower but has a more established community; building in-house is the most expensive short-term but creates zero license constraints.

---

Bottom line

FleetBase is the most complete open-source logistics OS currently available, and that ambition cuts both ways. The modular stack — FleetOps for dispatch, Storefront for ordering, Navigator for drivers, Pallet for inventory — covers what most courier and delivery operations actually need, and the developer tooling is genuinely built for engineers rather than bolted on as an afterthought. The white-label driver app is a real and concrete advantage over commercial tools that charge for that feature. But the AGPL-3.0 license creates hard friction for commercial embedders, the cloud pricing is invisible until you talk to sales, and the community is thin enough that you’re partly betting on a platform without a thick body of documented production deployments to reference. This is a tool for operations that have engineering capacity, a clear cost problem with existing logistics SaaS, and the risk tolerance to be earlier adopters. If that’s your situation, the infrastructure math makes FleetBase worth serious evaluation. If you need a proven, community-backed platform before putting your dispatch operations on it, give it another year.

If the self-hosting setup is the blocker, that’s precisely what upready.dev deploys for clients — one-time fee, done, you own the infrastructure.

---

Sources

1. Fleetbase Partners & Integrations | Build with the Best in Logistics Tech — fleetbase.io. https://www.fleetbase.io/partners
2. Shiv Thakker Speaks at GreenFreight Asia Sustainability Leadership Program — Fleetbase Blog, fleetbase.io. https://www.fleetbase.io/post/shiv-thakker-speaks-at-greenfreight-asia-sustainability-leadership-program
3. Fleetbase Storefront App | White-Label E-Commerce App for On-Demand Delivery — fleetbase.io. https://www.fleetbase.io/products/ondemand-app
4. Fleetbase Speaks at LogTech Asia 2021 Virtual Summit — Fleetbase Blog, fleetbase.io. https://www.fleetbase.io/post/fleetbase-speaks-at-logtech-asia-2021-virtual-summit
5. What Are Logistics Microservices? — Fleetbase Blog, fleetbase.io. https://www.fleetbase.io/post/what-are-logistics-microservices

Primary sources:

• GitHub repository and README: https://github.com/fleetbase/fleetbase (1,787 stars, AGPL-3.0 license)
• Official website: https://www.fleetbase.io
• Official documentation: https://docs.fleetbase.io/