EMBEDDED DECISION SERVICES
Add a bounded optimization, configuration-checking or re-planning capability to the product your customers already use. Keep your user experience; integrate the computational capability behind it.
Available products. A customer-specific workflow.
CLI · MCP · Headless
Vertical-software vendors, system integrators and teams building planning, allocation or configuration features.
A useful implementation has a specific job. The scope is built around your original requirements, environment and acceptance criteria.
A new solver interface can move work onto users instead of improving the application they already depend on.
Deliver the supported decision through your existing product. Agree the input and output contract so users get a usable recommendation or checked result in context.
A missing resource, changed limit or new requirement can invalidate a previously useful plan.
Re-evaluate supported revisions and return a new candidate or an explicit unresolved outcome, while preserving the relevant model and assumption identity.
Data mapping, error handling, distribution rights and escalation ownership are part of a commercial feature.
Package the selected capability with the required adapter, acceptance tests and responsibility split. License the scope actually embedded, not every product by default.
The final order identifies the selected products, integration work and operating responsibilities. Included components and work are not charged again.
A supported model and workflow for checking, optimizing or comparing the decisions your application needs.
Agreed data mapping, invocation, output/status contract and resource limits using CLI, MCP or headless access.
Evidence and outputs tied to the accepted input revision, with supported re-evaluation and failure behavior documented.
Integration documentation, acceptance results, licensed distribution scope and first-line/specialist support ownership.
A software vendor wants to offer a revised allocation inside its current planning screen after a resource becomes unavailable. The permitted model change and response budget are fixed before integration.
Explanation only—not a live product run or a claimed customer deployment.Choose the customer decision, supported rules and response contract. Confirm which revisions the implementation must handle.
Agree the supported models, execution environment and acceptance measures before committing to the delivery.
Choose the relevant capability.
Not every workflow needs every product.
Prototype access can use an eligible development plan. Customer-facing redistribution, embedded production, custom data adapters and support responsibilities require a named agreement; the monthly internal-use plans do not automatically include resale.
Not necessarily. A licensed embedded interface can support a feature inside your product while you retain your existing user experience.
Yes. The selected engine and required components can be scoped independently, subject to the product’s supported model and distribution terms.
No blanket claim is made. The model class and admitted revision operations are tested for the customer feature before acceptance.
UNISOLVE LinearSession adds supported current-original revisions, snapshots and exact reoptimization. Bound reuse requires preservation and a fresh attaining witness; the customer integration remains separately scoped.
Commission the model, integration and acceptance work needed for your task. Existing products stay independently available.
Commission one supported decision model, a scoped conflict analysis and a comparison of permitted repairs.
02 / Scoped customer programCommission a revision-aware workflow that keeps models, assumptions, results and evidence connected as inputs change.
One capability. A connected workflow.
A team to put it into practice.