DECISION SYSTEMS / SPINFORGEThe 64-entry portfolio

A useful answer.
A decision you can keep using.

Turn the capabilities you need into an approved model, a checked result and a repeatable customer workflow. Buy the tool directly or commission the integration around your decision.

Explore the three programs

Customer-specific engineering, not a new solver release. CLI · MCP · Headless across the product portfolio.

EXISTING PRODUCTS / EXPANDED INVENTORY

See the complete family.

SYNTHESIS

11 real products

Three layers, with Recursive Engine as the meta-system.

DISCOVERY

Core, applications & Bench

A shared Discovery Core for AMDE and Bio; a separate certified Gset offering.

COMPLETE CATALOG

64 named entries

Current modules, corrected lineage and explicit product relationships.

WHOLE-SYSTEM OPTIMIZATION

The connection
can change the result.

Joint configuration, decision-sensitive computation, checked memory, useful future options, exact reformulation and evidence-led improvement. Explore the role of every product and agree a matched system evaluation.

Explore all six connections 64-entry interaction map

Customer-specific integration opportunities—not added software entitlements or universal performance claims.

THREE CUSTOMER PROGRAMS

Start with the outcome.
Keep the scope clear.

Choose the decision you need to improve. Each program uses selected existing products and an agreed engineering scope.

01 / Scoped customer program

Explain & repair a constrained plan

Commission one supported decision model, a scoped conflict analysis and a comparison of permitted repairs.

02 / Scoped customer program

Maintain a recurring decision

Commission a revision-aware workflow that keeps models, assumptions, results and evidence connected as inputs change.

03 / Scoped customer program

Improve a computational workflow

Commission a bounded performance improvement with source identity, numerical acceptance and the appropriate checking evidence.

FROM REQUIREMENT TO REPEATABLE USE

Keep the meaning
through every change.

Select a stage to see the customer responsibility, delivery and evidence needed. This is a planning guide, not a running solver.

EIGHT CONNECTED WORKFLOWS

More than another engine.
A useful role in your system.

Six engineering-led paths and two research engagements. Each page identifies the existing foundation and the extra work needed for customer delivery.

10 / Customer-specific engineering

Executable decision models

Turn business rules, objectives and approved data into a reusable decision model your team can inspect and run.

11 / Customer-specific engineering

Conflict diagnosis & authorized repair

Explain a supported infeasible plan and compare explicitly authorized changes without silently weakening mandatory requirements.

12 / Customer-specific engineering

Decision history & reoptimization

Retain the model, assumptions and result history so changed requirements can be checked and re-evaluated without losing their meaning.

13 / Research engagement

Bounded contingency strategies

Study a strategy for explicitly modeled future events, preserving which decisions can use which information.

14 / Customer-specific engineering

Computational co-design

Connect a customer’s calibrated numerical model to constrained decision analysis and measured outcomes.

15 / Customer-specific engineering

Structure-preserving model preparation

Evaluate whether supported structure can reduce a model or connect it to a better-fitting engine while preserving the original problem.

16 / Research engagement

Optimization-change assurance

Pair a narrowly scoped semantic property check with separate numerical and performance evaluation of a computational change.

17 / Customer-specific engineering

Workload-fit evidence

Build a permissioned record of which engine and configuration fit a supported workload, including the cost of preparation and checking.

See all 17 solution workflows

DELIVERY GATES

The right proof.
The right permission.

A product interface does not create a multiuser cloud service or grant production-control authority.

01

Approve the model

Confirm units, source data, mandatory rules, allowed changes and the meaning of success.

02

Qualify the execution

Agree format and hardware compatibility, budgets, result states and required checking.

03

Observe before controlling

Compare with the accepted baseline before any customer-authorized production change.

04

Define the operating contract

Assign permissions, spending limits, retention, recovery, support and data-reuse rights.

UNISOLVE’s tested platforms remain macOS ARM64/Python 3.14 and Linux AArch64/Python 3.10. Windows and x86 release qualification remain open in the supplied inventory. A trusted local solver service is not a hosted security sandbox.

START THE CONVERSATION

Build a project brief.
Not another specification.

Choose the outcome and the areas to scope. Add a non-confidential description. Download your brief or carry it into an email inquiry. Nothing is uploaded or executed.

Review unchanged prices

A useful answer.A decision you can keep using.