Open Source Bringg Alternatives
A curated collection of the 1 best open source alternatives to Bringg.
The best open source alternative to Bringg is FleetBase. If that doesn't suit you, we've compiled a ranked list of other open source Bringg alternatives to help you find a suitable replacement.
Bringg alternatives are mainly ERP & Operations but may also be Logistics & Supply Chain. Browse these if you want a narrower list of alternatives or looking for a specific functionality of Bringg.
A modular logistics and supply chain platform for courier, delivery and field service operations, and for developers building on top of them.
Fleetbase calls itself an operating system for logistics and supply chain work, which in practice means dispatch, order management, live tracking and the planning around all three, gathered in one console. It targets e-commerce and retail delivery, food and beverage, courier services, field service scheduling and enterprise logistics teams.
The core is a PHP framework built around logistics abstractions, paired with a web console, a REST API, sockets and webhooks. Routing runs against an OSRM server, defaulting to the public one and swappable for your own instance or any OSRM-compatible service.
Operations are managed through a handful of views and subsystems.
- Order board: orders move across a Kanban board that reflects their current state.
- Order configuration: custom order types carry their own logic, rules, automation, activity flows and fields.
- Live maps: individual orders are tracked in real time, and the whole fleet appears on one live map.
- Service zones: delivery areas are drawn on the map and assigned to fleets.
- Identity and access: a dynamic IAM system governs permissions across the organization.
- Telematics: hardware devices and sensors report back for extra visibility into operations.
Extensions are the point of the modular design. A registry holds installable modules, and the Fleetbase CLI searches, installs, scaffolds and publishes them. Installation is a global npm install of that CLI followed by an interactive Docker-based installer, requiring Node 22, Docker and Git; the console then answers on port 4200 with the API on port 8000.
