Read it
orhof
Our operations-research library, published whole. Open any namespace and you'll see the inputs, outputs and ranges written down.
github.com/Flexiana/orhofComponents we license to go inside your product
Tell us what your product is missing, or which calculation now costs you the most to run. We agree an acceptance test on your own workload. If the component does not pass it, you pay only for the test.
What we mean by a component
We write this down before we connect anything.
-
Inputs and outputs
Written down, with the shapes and the ranges.
-
Failure behaviour
What it does with bad input, a workload that is too big, or an answer that would take too long.
-
Fallback and rollback
How you turn it off without taking your product down.
See our work before you call
The people who wrote these build the components we license.
Verify it
Rainbow
A dependent-type theorem prover in Clojure, with kernel-checked theorems about 222 of 222 catalogued operations-research algorithms.
How the proof worksRun it
Four calculators
Two of them return the exact optimum. What you type stays in your browser, and you don't need an account.
Run one on your numbersHow it is bought
You know the price of each stage before it starts.
-
One
Paid validation
We run it on your workload. You keep the benchmark, and it shows whether the gain holds at your scale.
-
Two
The integration
The component, the integration, the acceptance test and the rollback path. Any piece of work we don't do gets a named owner.
-
Three
A recurring licence
Maintenance, versioning and support, priced on what the component is worth to your product.
What it saves, and what it costs you
We work out what your customer saves, how much of that you keep through price, retention or lower delivery cost, and what you pay us.
You see all of these numbers. We charge a licence fee and take no share of what you earn from it.
Questions about licensing a component
What exactly do we receive?
An engine, library, API, plug-in or deployable service, plus the acceptance test it must pass on your workload.
Does it have to run on your infrastructure?
No. It can run inside your own environment, and your data stays with you.
Why license this instead of building it?
Building it yourself takes a year of specialist work, on something that is not your core product.
Who owns the integration?
We name the owner before we start, usually your engineers with us alongside.
Tell us what the component has to do
Send us the inputs, the workload and what it has to beat. Jiri or Ivo will reply and tell you if we have a method that fits. Talking to us costs nothing.