Philosophy · the part that never changes
Why Unfragile
There are three kinds of things in the world. Fragile things break under stress — the teacup, shipped in bubble wrap, praying nothing shakes. Robust things resist stress — the rock, unchanged by the storm, unchanged by anything. And there is a third kind, named by Nassim Nicholas Taleb, that most languages don’t even have a word for: things that gain from disorder. Muscles after strain. Immune systems after exposure. Good ideas after criticism. Taleb called it antifragile. We took it as a name: Unfragile.
The name is a commitment, not a decoration. This company is built to get stronger when things get chaotic, uncertain, and difficult — because chaos is precisely what we process. Our raw material is the disorder of the software universe itself.
Why the agent economy needs an unfragile layer
Software is now shipping faster than anyone can vet it. Agents are invoking tools their models have never seen, published yesterday, by strangers, with claims nobody checked. Every wave of that chaos makes an ordinary directory more wrong — and makes verification more valuable. Stress on the ecosystem is demand for us. That is the structural bet: we don’t need the agent economy to be orderly; we need it to keep growing, changing, and surprising everyone. The more it does, the more a fresh, tested, signed answer is worth.
How an unfragile company is built
Taleb’s barbell: cap the downside, leave the upside open. Our attempts — individual products, pages, bets — are deliberately fragile: small, cheap, written with their kill criteria before a line of code, allowed to die. The company is the opposite: its identity survives any attempt’s death, its archive only grows, and every failure becomes a test case that makes the next answer better. Attempts are fragile so the company doesn’t have to be.
The commitments that never change
- Rankings are never for sale. Vendors may pay for deeper verification of their own software — never for the answer. The day a ranking can be bought, the answer is worthless.
- We never operate what we rank. We test, sign, answer, and route. We don’t build, host, or run the software we judge — a referee who owns a team isn’t a referee.
- Honest tiers, always. “Not yet verified” is never “failed.” We never publish a claim our methodology can’t carry, and when nothing qualifies, the answer is an honest no — not a guess.
- The archive is the asset. History is never reset by a refresh. What we observed about the software universe, and when, compounds — it is the one thing that cannot be rebuilt by a competitor with a bigger cheque.
Everything else about Unfragile is allowed to change — the pages, the products, the envelopes, the business model. This page is not.