Built to be read.
Apache 2.0, no strings. The parts of Inflexa that decide what happens to your data, and how the result can be trusted, are open. Read what it does, then change it.
curl -fsSL https://inflexa.ai/install.sh | bashRecommended. Downloads a prebuilt binary.
Apache 2.0 · No account required · Requires Docker or Podman
What is open, and what is not.
Vague answers here are how open-core promises die. So: specifically.
Open — Apache 2.0
The orchestrator
The thing that plans your analysis and decides what runs.
The agent harness
The loop that reasons, calls tools, and writes the code.
The skill packs
Every method the agent knows, and how it knows to use it.
The sandbox images
The environment your analysis actually executes in.
The provenance substrate
How results are recorded, signed, and verified.
Not open
The Inflexa name and logo
Trademarks, not code. Fork the software, ship it under your own name.
Inflexa Cloud
The hosted service. It is how we pay for the rest — and it is the only thing here you can buy.
Notice what is not on this list: nothing that decides what your results are, reasons about them, or proves where they came from. That machinery stays open, and it stays open permanently.
Three promises, and what they cost us.
Existing open-source features will not move behind a paywall.
Not when investors ask for a tighter moat. Not when an enterprise deal makes it tempting. If it is open today, it is open tomorrow.
The software does not depend on us to work.
There is no Inflexa service in the loop. No account, no licence check, no phone-home. If we disappeared, your install would keep running.
We do not harvest your work.
Your analyses are not training data for a model you cannot see. The open core improves in public, through code and review — not by watching you work in private.
A closed system can ask you to trust it. An open system can be tested.
Trust in science is not a feeling, and it is not a brand. It comes from the possibility of inspection. Can you see what happened? Can you rerun it? Can you find the bug? Can someone else check the logic?
A closed company can give you a provenance record. It can show you a log and export a report. But if the system that produced the record is closed, the record is still a favor — and favors change with pricing, policy, acquisition, and strategy.
Real provenance is not a receipt. It is the ability to understand the thing that produced the receipt.
The more powerful a scientific tool becomes, the less acceptable it is for it to be opaque. When a system only formats tables, opacity is annoying. When it chooses methods, interprets results, and guides experiments, opacity becomes dangerous.
We won’t pretend to be vendor-neutral.
This is a company-led open-source project. Inflexa, Inc. funds the work and holds final decision authority. It is not a foundation, and we are not going to dress it up as one — you should know exactly what you are depending on.
What that buys you is the licence, and the licence is the real guarantee. If we make a decision you cannot live with, Apache 2.0 means you can fork the project and keep going without asking us.
Go read it.
The orchestrator and the provenance library are both Apache 2.0. Start wherever you are most sceptical.