Often it's something you already have, like your pricing personalization, or an internal process that used to take 20 minutes and now takes 4 hours.
We deliver a tenfold return. We show you how much more you can earn or save, help you get there, and our support costs a tenth of it or less.
Our code is public. You can read it.
Where our software runs
100M+ people
use Livesport. We built nine of its internal systems. We have also built for Alza, Guaranteed Rate, Reify Health and Crossbeam.
How we check the maths
We wrote our own theorem prover.
It is called Rainbow. Every number we give you goes through it first.
See Rainbow01 Gitrevio
Gitrevio connects to your Git, tickets, CI and HR tools and shows, project by project, where engineering money goes and what the business got back for it. Pricing depends on the value it brings you.
See Gitrevio
02 The Studio
Systems for e-fuels plants, ports and the back office of your business, with operations research built in. We calculate what a better way would earn you, using your own numbers. Then we build it and run it.
See what we solve
03 The Decision Lab
We try exact algorithms and machine-checked proofs on real company data. The ones that win go into the systems we build for clients.
Enter the Lab
Gitrevio
Gitrevio shows where your engineering money goes and what the business got back for it, project by project.
Reade-Fuels and hydrogen
e-SAF, e-methanol and hydrogen plants, modelled against real weather and power prices, from design to daily dispatch.
ReadPorts
Berths, cranes and yard planning, hydrogen refuelling and bunkering, and port energy.
ReadProject margin
For each project, what it will cost to finish and the chance it ends in a loss. You see it while a manager can still act.
ReadCapacity and scheduling
What to accept, schedule or defer when you are short of people and time.
ReadRemediation and warranty
Defects, claims or cases, ranked by what each one costs you while it waits.
ReadCritical software
A machine-checked proof that the rule holds for every possible input.
ReadIf it is not on this list, tell Jiri or Ivo about it. Talking to us costs nothing.
We find, prove and build. Then we operate what we built and keep making it better. Each stage has its own fee.
Two to three weeks for a fixed fee. We look at how the process works and what it costs, and come back with a number and a plan.
Four to eight weeks. We test the riskiest part on your own data, with a solver, a prototype, a proof or a shadow run.
What worked becomes production software, with monitoring and a manual override built in.
Each product started as client work that paid off.
For founders and investors
Shows where your engineering money goes and what the business got back for it.
Explore GitrevioOpen-core theorem prover
A theorem prover where proofs are ordinary data. It comes with kernel-checked theorems about all 222 catalogued operations-research algorithms.
See RainbowWe build in Clojure. Rainbow, orhof and chachaml are open source, and the book behind them is Applied Higher Order Functions.
The partner who starts the project stays on it until the end, and after.
First you pay for an answer to the riskiest question. The big project comes later, if that answer says it is worth it.
The best projects start with something a company has done the same way for years, because it works well enough. So I ask what a better way would be worth.”
Jiri Knesl, founder of Flexiana
Author of Applied Higher Order Functions
We work out what a better solution would earn you first, then we build it ourselves. The people who estimate the work also write the code.
No. Talk to us first, it costs nothing. Many clients go straight to building. If you want the numbers in writing before you decide, we can run a short audit first.
Look at what we have built. We wrote nine internal systems for Livesport, which more than 100 million people use. The hard parts of our own tools are open source, and you can read a worked sample of the audit findings. And the first step is a fixed-price audit, so you can try us on a small piece of work.
Good, we work best with one. We bring operations research, formal methods and product engineering, and we turn the analysis into a system that runs. Your team knows the business and keeps the baseline we build.
Jiri or Ivo will read it and tell you what fixing it could be worth.
