Arclane

PRODUCT / HOW IT WORKS

Five stages, in your account.

Ingest your stops and fleet, build the matrix once, search, validate against your constraints, and commit a plan your dispatchers can override.

PIPELINE / STAGES

  1. 1

    Ingest

    Stops, windows, demand, skills; vehicles, capacities, depots, shifts. CSV, JSON, or API.

  2. 2

    Matrix

    The travel matrix is built once, in your VPC, from your coordinates or your own road-network times.

  3. 3

    Search

    Construction to a first feasible plan, then local search and ruin-and-recreate drive the objective down.

  4. 4

    Validate

    Every run is checked against capacity, windows, skills, and duty time. Nothing infeasible leaves the solver.

  5. 5

    Commit

    Return the plan with per-run sheets and per-stop reason codes. Lock completed stops and replan the rest.

SOLVER / WHAT IT IS

A metaheuristic. We say so.

Construction plus first-improvement local search, 2-opt, or-opt, relocate, swap, with a ruin-and-recreate kick to escape local optima. No black box, no "AI." The same solver runs in your browser above the fold and in your cluster in production.

MATRIX / ENGINE

Compute once, re-plan free.

A metered API charges you for the matrix on every call. Arclane computes it once and keeps it warm; re-planning through the day costs you nothing but CPU you already own.

FAQ / HONEST

Why not just use OR-Tools?

You can, and for a batch job on one machine it is excellent. What OR-Tools does not give you is a solver that compiles to WebAssembly and runs in a browser tab, a packaged container with a Helm chart and reason-code explanations, or a support contract. Arclane is the productised, self-hostable version of the thing you would otherwise assemble and maintain yourself. If your team is happy owning that, use OR-Tools, we mean it.

Is it faster than a hosted API?

Latency depends on your hardware, not our queue. On 8 vCPU we take roughly ten seconds to a low-single-digit gap on a 1,000-stop instance. The benchmarks show the numbers, including where we lose.

Does my data leave my account?

Never. Egress is zero bytes by design. See security.

Read the explainability model.

Every unassigned stop tells you why, in JSON your systems and your dispatchers both read.

Explainability → Deployment →