Built into how you plan, whichever way suits you.
Gradient Path fits the way you already work — as a library inside your software, as a complete application built around your problem, or, coming soon, through a cloud API.
A library, a cloud API (coming soon), or a finished application.
As a library 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 cloud API (coming soon)
Gradient Path hosted on AWS or Google Cloud. Your software connects over an API, sends the problem and gets the solution back — no solver to install or run yourself.
As a complete application
We build and deliver the whole thing for a specific planning problem — the data model, the constraints, the solver configuration and the output your planners actually use.
What to expect.
No solver lock-in. The platform runs on open-source or commercial back ends. You are not obliged to buy a license to get a solution, and when you run it as a library, you are not prevented from using one you already have.
Run it yourself, or let us run it. As a linked library, it runs where your software runs: there is no round trip to a third-party endpoint and no operational data leaving your estate to get a solution back. Once the cloud API is available, you can instead send the problem to us and get the solution back over an API, with nothing to install or operate.
Tuned to your window. How long the platform is allowed to search is a setting, not a fixed property. The trade-off between solution quality and time to solution is one we set deliberately with you — see how the platform works for why that trade exists.
Not sure which way in fits? Ask us.
Tell us how your planning software is built today, and we will suggest whether a library, the cloud API or a complete application fits best.