Good solutions, fast.

Vroom is an open-source route optimization engine written in C++20 that solves complex vehicle routing problems (VRP) in milliseconds.

The project is maintained by Verso. If you want to get started as quickly as possible with route optimization, you want white-glove support to increase the ROI from your optimization project and/or you need access to the best possible data for even more accurate route timing, you should use the Vroom Premium API.

Vroom is ideally suited to situations in which route optimization has to be done quickly, both to react to changes and new requests and to iterate on your routes to find the solution that works best for all stakeholders.

Vroom doesn't replace domain expertise. It allows fleet managers and business owners to apply their domain knowledge and understanding of the company culture to larger, more complex optimization problems than they could manage manually.

The open source project is ideal for companies who want to control their own infrastructure, have the technical expertise to do so and can manage their own data integration. If you would rather not manage your own infrastructure, if you want access to expertise around route optimization or if you want more accurate ETA relying on enhanced speed estimates, consider using the Vroom Premium API.

Vroom solves several well-known types of vehicle routing problems (VRP).

• TSP (travelling salesman problem)
• CVRP (capacitated VRP)
• VRPTW (VRP with time windows)
• MDHVRPTW (multi-depot heterogeneous vehicle VRPTW)
• PDPTW (pickup-and-delivery problem with TW)

Vroom solves all of the above routing problems at the same time — and delivers the optimized route in milliseconds, even when complex variables are involved.

Vroom models a VRP with a description of resources (vehicles), single-location pickup and/or delivery tasks (jobs) and pickup-and-delivery tasks that should happen within the same route (shipments).

• Delivery/pickup amounts on arbitrary number of metrics
• Service time windows
• Service duration
• Skills
• Priority

• Capacity on arbitrary number of metrics
• Skills
• Working hours
• Driver breaks
• Start and end defined on a per-vehicle basis
• Start and end can be different
• Open trip optimization (only start or only end defined)

Vroom works out-of-the-box on top of several open-source routing engines.

• OSRM
• Openrouteservice
• Valhalla

Vroom can also use a custom cost matrix computed from any other source.

• The demo frontend provides a simple user interface for quick tests.
• The demo server makes it easy to send sample optimization requests for testing purposes.

Several options are available to get vroom running on command-line.

1. Build from source following the wiki instructions.
2. Use vroom-docker.

Refer to this wiki page

vroom-express is a simple wrapper to use vroom with http requests. It's already bundled in the vroom-docker setup.

The project can also used as a library from any C++ project, refer to this wiki page.

Github Actions are used to check the build across various compilers and settings.

Several sets of instances are used.

1. Benchmark instances from papers (see wiki page with results).
2. Custom random instances generated to target typical use-cases and constraints settings.
3. Real-life instances.

Academic and custom benchmarks are heavily used during development for each new core feature. Every new release is checked against all benchmarks classes to spot potential regressions with regard to both solution quality and computing times.

To cite Vroom in publications, please use:

@manual{vroom_v1.14,
   title = {{Vroom v1.14, Vehicle Routing Open-source Optimization Machine}},
   author = {Coupey, Julien and Nicod, Jean-Marc and Varnier, Christophe},
   year = 2024,
   organization = {Verso (\url{https://verso-optim.com/})},
   address = {Besançon, France},
   note = {\url{http://vroom-project.org/}}
 }