Why Flagon exists

There is already plenty of software, and plenty of companies making it. We started another one anyway. Here is why.

Why we started

We wanted to work somewhere that operated the way we thought a company should, and it was easier to build one than to keep waiting for it to appear.

Most of us have worked at places where the stated values and the actual behavior drifted apart: the handbook said one thing, the calendar said another, and decisions arrived as law from rooms you were never in. None of that is unusual. It is just tiring, and it makes the software worse, because the people closest to the work stop bothering to have opinions. Flagon is the attempt to not do that. Not a manifesto about it, an actual company, run out loud so you can check whether we mean it.

The one bet

Everything here rests on a single bet: that building in the open is an advantage, not a liability.

Trust is not something you buy with a marketing budget. It is a track record someone can read. So we publish the track record as we go, the handbook, the roadmap, the reasoning, the misfires, and when we get something wrong the wrong version stays in the git history. Working this way makes the work sharper too: a decision you have to defend in public tends to lose its weak points before it ships. That is the whole thesis. The rest of this handbook is what it looks like in practice.

What we are not doing

We are not optimizing for a quick exit. There is no acquisition we are steering toward and no plan to flip this to someone bigger. The goal is boring and hard: to still be here in a decade, still making good things, still a company worth working at. That one choice quietly settles a lot of the others, from how we pay people to how we make money to how fast we grow. It's one of our values, and the reason staying alive matters more than looking impressive.

If watching a company try to do this in public sounds interesting rather than terrifying, you are probably our kind of person.