Embedded in your systems, not bolted on.
Gradient Path becomes part of your own software rather than sitting beside it as another system to integrate, operate and explain.
An engine, or a finished application.
As the engine inside your product
Your team owns the product and the domain model; Gradient Path does the optimization. It ships as a library with interfaces for C++ and Python, and no dependency on any single commercial solver.
As a complete application
We build and deliver the whole thing for a specific planning problem — the data model, the rules, the solver configuration and the output your planners actually use.
What integration actually involves.
No solver lock-in. The engine runs on open-source or commercial back ends. You are not obliged to buy a licence to get an answer, and you are not prevented from using one you already have.
It runs where your software runs. As a linked library rather than a service, there is no round trip to a third-party endpoint and no operational data leaving your estate to get a plan back.
Tuned to your window. How long the engine is allowed to search is a setting, not a fixed property. The trade-off between answer quality and time to answer is one we set deliberately with you — see how the engine works for why that trade exists.
Tell us about the plan you are trying to improve.
If you run an operation where scheduling or routing decisions carry real cost, we would like to hear what it looks like — and what the best plan would be worth to you.