Solver as a Service
Describe an optimization problem in a manifest, send the problem records, and get back a solution with a certificate, or a typed refusal that says why there is none. The hosted solver runs at solver.helixor.dev.
Try it now
Open the solver console: pick a problem type, load a dataset and solve it. Sign-in required; email hello@helixor.ai for access.
How a solve works#
Every request crosses the same boundary:
validated manifest + explicit problem records
-> admitted decision model
-> solver policy
-> solution + certificate, or a typed refusal
A manifest declares a problem type: what it optimizes, the inputs it takes, the constraints it can enforce and the presets it offers. You can send a manifest with a single solve while you develop it, or package it as a solver pack and install it as a reusable problem type.
Start here#
Build a problem type, step by step
From two employees and two shifts to an installable retail-scheduling problem type with a generated client and a manifest-driven interface.
Problem typesThe manifests the solver ships
Routing, rostering, field service, scheduling and more: objectives, inputs, constraints and presets for each.
ReferenceManifest format
Every top-level key of a manifest, from the schema the solver validates against.
ReferenceHTTP API
Solve, job status, feasibility checks and recommendations, with request and response bodies.
DeploymentEmbedded or hosted
Run the same routing and rostering problems in your process or on the hosted solver.
The tutorial, problem types and reference on this site are generated from the solver's own sources: its tested tutorial, the manifests it ships and its published contract.