Commercial · in production
01Gitrevio
Engineering value intelligence. Connect plans, delivery and business context to diagnose risk, capacity and AI-era productivity: without reducing engineers to a single activity score.
Explore GitrevioProducts
Five products, each of which began as a problem we kept hitting
We did not set out to have a product portfolio. Each of these started inside client work or our own, as the same problem turning up more than once, and became a product only once the method had held up and somebody had paid for what it produced. Until then a capability stays a research artefact or an internal tool, and most of ours still are.
The portfolio
The five
Commercial or open source, each one built and running somewhere. The label on each says which it is and how you get hold of it.
Open source · Clojure theorem prover
02Rainbow
A Clojure-native theorem prover that treats terms, proofs and provenance as composable data. A small trusted kernel checks what an untrusted engine proposes.
See RainbowOpen source · MIT · shipped v0.7.0
03chachaml
REPL-first MLOps for Clojure, with a web UI, an MCP server and chat-with-data. Track experiments and models without leaving the REPL.
View chachaml on GitHubOpen source · v1.1.0 · Apache-2.0
04Infix
Optional infix notation for Clojure: write a * b + c / d, and it compiles to ordinary Clojure forms with no runtime cost. Arrow lambdas, threading as an infix operator, and Java method chaining. One dependency: Clojure itself.
View Infix on GitHubOpen source · Apache-2.0
053TL
Typed Talking To LLMs. A small data format, CSV with types, foreign keys and enums, multiple tables in one file, so a language model reads structured data without guessing at it. Parsers in Python, JavaScript, Clojure and Go, with a full type and syntax reference.
See 3tl.orgWorking in Clojure or on the JVM and putting models into production? What chachaml means for an MLOps team covers the workflow it replaces and the decisions underneath it: when to retrain, what to promote, and what an experiment is worth running.
Building something of your own and missing a piece of it? Some of our work is licensed as a component that goes inside someone else's product and is never sold as a product of ours — how that works, and what we decline.
How a product earns its place
What it takes to become a product here
Two things, both of them: the method works, and somebody will pay for what it produces. A capability that meets one and not the other is interesting and stays on the shelf.
Most of these started inside client work, as the same problem turning up more than once. Until the method holds and the outcome is worth paying for, it stays a research artefact or an internal tool. That is why the list is short, and why each item says exactly what it is and how you get it.
FAQ
Questions about the products
How does a capability become a product here?
Only when two things are true: the method works, and someone will pay for what it produces. Most of these started inside client work: the same problem turning up more than once. Until the method holds and the outcome is worth paying for, it stays a research artefact or an internal tool.
What do the labels, commercial, open source, mean?
They say how you get each one. Gitrevio is commercial and in production. Rainbow is open source under the Eclipse Public License or GPL, the same dual licence Clojure uses, and its repository publishes with the release. Flexiana Atelier are commercial creative products. chachaml is open source under MIT and published to cljdoc. 3TL and Infix are open source under Apache-2.0. Each item says what it is and how to obtain it.
Why is the list so short?
Because we only call something a product once the method has held up and somebody has paid for what it produces. A capability that has done neither is a research artefact or an internal tool, and we have plenty of those. Each item on this page has cleared both bars, and the list stays short because of it.
How do I try each one?
Gitrevio has a dedicated product site at gitrev.io. Rainbow, chachaml and Infix are on GitHub. The Atelier products, LiveSet and MrKicksy, live at liveset.app, and 3TL is at 3tl.org. Each product page links out to where you can see or use it.
What are chachaml, 3TL and Infix?
chachaml is REPL-first MLOps for Clojure: a web UI, an MCP server and chat-with-data, so you can track experiments and models without leaving the REPL. It is MIT-licensed and shipped v0.7.0. 3TL is Typed Talking To LLMs: a small, open data format under Apache-2.0, CSV with types, foreign keys and enums, multiple tables in one file, so a language model reads structured data without guessing at it. It ships parsers in Python, JavaScript, Clojure and Go. Infix adds optional infix notation to Clojure, a * b + c / d compiles to ordinary Clojure forms with no runtime cost, in four namespaces, 83 tests and one dependency.
What if my problem is not one of these products?
Bring us the repeated, expensive decision. A partner will say whether it warrants a product, an audit, or a different route, and if none of them fits, that is the reply.
Bring us a hard problem
If your problem is not one of these
Tell us where the same expensive decision keeps recurring. A partner will say whether it warrants a product, an audit, or a different route.