SpinForgeA Garmo Labs CompanyDiscuss a workload
UNIVERSAL CONSTRAINT SEARCH

GARMO UCS.

Work within the rules.
Search beyond the obvious.

A native constraint-search engine for supported logical, integer and engineering decision models.

Discuss GARMO UCS
UNIVERSAL CONSTRAINT SEARCH
Conceptual product artwork for GARMO UCS, not physical hardware
Conceptual product artworkDrag to explore ↔
MODEL / METHOD / RESULT
Available nowCLI MCP HeadlessChoose your access mode

THE PRODUCT, IN PRACTICE

An answer must fit the rules.
Not just improve the score.

When a decision includes compatibility, capacity and logical requirements, a high-scoring answer can still be unusable. GARMO UCS lets teams express supported rules and objectives as a constraint model, search for acceptable decisions and inspect the returned evidence. It provides an engine for a defined workflow without requiring unrelated inference applications.

BUILT FOR
Engineering configuration, planning-software and resource-allocation teams with supported rule-rich decision models.
CHALLENGES → PRODUCT RESPONSE

The problem you face.
What GARMO UCS changes.

01

Good scores can violate hard requirements

A proposed configuration is not useful if mandatory relationships or resource restrictions are broken.

UCS searches within the supported constraint model so the team can assess candidate decisions against the rules it actually encoded.

02

Requirements need a shared representation

Rules scattered across separate scripts are difficult to connect to one optimization objective.

The engine’s supported model interface brings variables, logical relationships, restrictions and the objective into a defined solving task.

03

A result needs a clear stopping state

A team needs to know whether it has a candidate, a bound or an applicable proof—not only whether execution finished.

The selected UCS mode exposes its available result, objective, bounds, replay and proof artifacts for review under the qualified scope.

WHAT YOU GET

A defined capability.
A useful output.

The product scope below describes the capability and outputs to confirm for your release. Custom integration, operated delivery and additional engineering are separately agreed.

01

A constraint-model interface

Access to the variables, rules and objectives supported by the selected release.

02

A native search engine

Solving for the agreed Boolean, integer and constraint problem classes.

03

Result and evidence outputs

The assignment, objective and available bounds or proof records appropriate to the run.

04

A licensed integration boundary

Defined runtime, input classes, resource limits and support for the customer workflow.

AVAILABLE NOW

One product.
Three ways to work.

GARMO UCS is fully available with CLI, MCP and headless access. Use the interface that fits your terminal, your agents or your automated workflow.

01 / CLI

For your terminal.

Run the product from a terminal or script, alongside the tools your team already uses.

Get CLI access
02 / MCP

For your agents.

Connect MCP-compatible clients and agents to the product’s exposed capabilities.

Get MCP access
03 / HEADLESS

For your workflows.

Operate without a graphical interface in unattended, scheduled or pipeline-driven work.

Set up headless access

Product-specific inputs, hardware requirements and result guarantees still apply. An access mode does not change your license or deployment scope.

Explore all product interfaces
EXAMPLE CUSTOMER WORKFLOW

Choose a configuration under mandatory rules

An engineering team needs to select a supported combination while preserving capacity and compatibility requirements.

Illustrative use of the supported scope, not a customer case study or a measured result.
  1. 01

    Express the accepted choices, hard rules and objective in the supported interface.

  2. 02

    Run the model within the agreed execution limits.

  3. 03

    Inspect the returned candidate and available completion evidence before using it.

EXPLORE THE WORKFLOW

A clear path
through the work.

Illustrative workflow. No customer computation is performed on this page.

01 / Model

Define supported variables, requirements and the original objective.

IN YOUR WORKFLOW

Start with your task.
Agree the useful outcome.

Engineering configuration, planning-software and resource-allocation teams with supported rule-rich decision models.

What you bring
The supported rule model, objective, deployment configuration and required result-evidence level.
What a useful evaluation measures
  • Satisfaction of the original encoded requirements
  • Candidate quality within the agreed budget
  • The precise evidence supporting the completion status
Where it fits
Use the selected product in a qualified customer environment, or agree a defined implementation with SpinForge. A hosted or managed service is quoted for its actual operating responsibilities; it is not automatically included with software access.
QUESTIONS BEFORE YOU BUY

A clear scope.
No hidden assumptions.

How can we use GARMO UCS?

CLI, MCP and headless access are all available. Run from a terminal or script, connect an MCP-compatible client, or use the product without a graphical interface. Choose the mode during onboarding and receive its setup instructions. Runtime requirements and supported operations remain product-specific.

What is the important product boundary?

Qualification defines the native capabilities and interfaces of the delivered release. A constraint-search engine is not automatically a complete application for every industry. GarmoForge and UNISOLVE remain separate products; shared functions do not imply completed cross-engine integrations.

What comes with the selected license?

The agreed GARMO UCS release, its supported interfaces and outputs, the applicable checks and the support stated in your order. The plan defines users, workflow, environment and capacity. Source-code transfer, unrestricted redistribution and bespoke engineering are not automatically included.

Can SpinForge implement or operate it for us?

Request a scoped engineering or operated-service proposal. It identifies what our team delivers, where the workload runs, infrastructure costs, acceptance requirements and ongoing support. Your software subscription alone does not activate a hosted runtime.

Explore engineering
How do we establish fit before production?

Agree the model or workload, current baseline, environment, required output and acceptance tests. Evaluate the selected release against those conditions. A product description or a test count does not establish a gain on a different customer workload.

Plan an integration
ENGINE LICENSINGBy proposal

Focused, enterprise, multi-site or embedded scope.

Licensing options
PUT GARMO UCS TO WORK

Tell us what needs to improve.

Bring a representative workload and the result your team needs. We’ll define the product, deployment and engineering scope around that task.

Discuss this workflow
Related products, workflows and system connections +
ONE PLATFORM / OR A DIRECT PURCHASE

Checked Decisions
with GARMO UCS.

Activate this capability inside a qualified checked decisions workflow. Compatible methods and required shared checking are included once within that workflow; the product remains independently purchasable.

Capacity, release, environment, result contract and operating responsibilities are specified before activation. Choosing an additional method is not permission to add an unrelated workload or unqualified deployment.

Explore Checked Decisions Choose workflow capacity
FROM PRODUCT TO CUSTOMER WORKFLOW

A useful outcome.
A defined delivery.

Commission the model, integration and acceptance work needed for your task. Existing products stay independently available.

Explore decision programs
START WITH THIS PRODUCT

Use the software directly or ask us to scope the implementation.

YOUR NEXT MOVELET’S MAKE IT COUNT

Put it
to work.

One capability. A connected workflow.
A team to put it into practice.

patrick@garmolabs.com

FIND YOUR CAPABILITY