Optimatika · makers of ojAlgo

Optimisation in pure Java, with more solving power when you need it.

ojAlgo gives Java developers LP, QP and MIP solvers in one Maven dependency — no native code, nothing for the platform team to veto. Need more capacity? Point the same model at the Optimisation Service running in your own cluster. Stuck? Ask the people who wrote it.

Start free Subscriptions from EUR 175/month, support included

The free tier is the Optimisation Service on one core with ojAlgo’s own solvers. Pull the image and put a real model through it.

var model = new ExpressionsBasedModel();

Variable x = model.newVariable("x")
    .lower(0).weight(3);
Variable y = model.newVariable("y")
    .lower(0).weight(2).integer();

model.newExpression("capacity")
    .set(x, 1).set(y, 2).upper(14);

var result = model.maximise();

One dependency. The same code whether it solves in-process or on the Service.

Since 2003 — public releases, public changelog
MIT licensed, always
Zero dependencies
Open benchmark harness
Support answered by the maintainers

Optimisation Service

When a model needs more solving power than pure Java can deliver, point it at a solver server running in your own cluster. Your model code stays the same — only the solving moves. No native code in your application, no licence servers.

How it works

ojAlgo Support

A private line, by email, to the people who develop ojAlgo, the Service and the solver integrations. Formulation, solver choice, why a model behaves the way it does. Included at every paid step.

What it covers

Custom Work

When the question turns out to be a project: model review, reformulation, performance investigation, financial systems. Fixed-scope, one day or one week, priced before anything starts.

Sizes and prices

Start in pure Java, scale without rewriting

You begin with one Maven dependency and no infrastructure. When a model needs more solving power, the Optimisation Service is there — same model code, same API. The upgrade is a deployment change, not a rewrite.

Keep control of your stack

No native binaries in your application, no JNI, no licence servers from other vendors. The solver infrastructure runs in your cluster, in your cloud account. No data leaves your environment.

Talk to the people who wrote it

Support is included at every paid step. Questions go to the developers who maintain the library, the service and the solver integrations — not to a support desk reading documentation.

No lock-in

ojAlgo is MIT licensed and the modelling is solver-agnostic. The code you write is always yours, and it never stops working because you stopped paying. The Optimisation Service is one way to solve — not the only way.