Solver engine · Beta · Routing & Sequencing
QG-ROUTE.
In what order, and along which path? QG-ROUTE reduces routing and sequencing cost against the solver you run today — proven on your own data before you change a single system.
Overview
Routing & Sequencing.
Routing cost reduction
Against your current solver on historical data. Labeled preliminary until independently revalidated.
PreliminaryBenchmarked first
We measure against your current method before you change anything. No rip-and-replace to find out if it helps.
Your constraints
Time windows, capacities, skills, and service levels you already operate under — respected, not simplified away.
Canonical problems
What QG-ROUTE solves.
Industries
Where it's already at work.
QG-ROUTE is the most mature engine — it's exercised across five of our eight industries.
Methods
Quantum-inspired and quantum-hybrid.
QG-ROUTE formulates routing and sequencing problems into canonical QUBO/Ising form and solves them with quantum-inspired evolutionary and swarm search, quantum annealing on rugged routing landscapes, and hybrid quantum-classical decomposition for large fleets. Most workloads execute on classical accelerators today; each job is routed to whichever solver measurably wins, and which one that is stays visible to you.
Research behind this engine
Quantum route optimization for logistics — the working code and benchmark methodology QG-ROUTE runs on, developed at QuMatrix.
Proof of value
A paid, scoped, time-bound pilot.
We hold every published number to the same standard: independently reproduced and methodologically documented before it loses the "preliminary" label. If we can't defend it, we don't print it.
FAQ
Straight answers.
Is this actually quantum?
Yes — QG-ROUTE runs on hybrid quantum-classical and quantum-inspired optimization, with a direct path onto quantum hardware as it matures. Today most workloads execute on classical accelerators; we route each job to whichever solver measurably wins, and we're transparent about which one that is.
What's the maturity?
Beta. It runs real benchmarks against real operational data, but it is not a general-availability product yet. We label it beta because it is beta.
Do I have to replace my existing systems?
No. The benchmark needs only a data export. Integration with your systems happens later, and only if the numbers justify it.
How is the 6%+ figure measured?
Against your current solver, on your historical routes, with identical constraints. It is preliminary and stays labeled that way until independently revalidated. The full methodology is shared under NDA.
What data do you need to start?
Historical routes or sequences, the operating constraints, and current costs. Anonymized or sampled data is fine for a first benchmark.
See QG-ROUTE run against your data.
Thirty minutes to scope a pilot, a clear benchmark on your own data, and an honest read on whether it's worth going further.
Contact us →