A fix session, step by step.
Every fix moves through the same five steps, and anyone on your team can drive them. The model researches and proposes, the contributor decides, your host runs the checks, and an engineer reviews before anything merges.
Five steps. Anyone can run them, and an engineer has the last word.
Each step names who does it.
Most coding tools stop at "here is a suggested change." Fixroom is built around what happens next. The model only does research and proposes changes. Every step that changes something belongs to a person or to your host.
Fixroom · Sheet A-1 · How a fix moves · Business view, not to scale
Who can do what.
A fix doesn't need an engineer to write it. It needs an engineer to review it. Fixroom's roles are built that way.
Every level is opt-in, one step at a time.
Patching, delivery and operations are three separate settings. Turning on pull requests doesn't make Fixroom take more risk. The defaults below are what a fresh install does.
FIXROOM_KILL_SWITCH=true, nobody can release it through the API.Run it on your own server.
Fixroom is proprietary software from Barox Labs, licensed per developer. Every plan comes with a written licence, the free one included.
- ServerDebian or Ubuntu
- Repositorieson GitHub
- Model endpointOpenAI-compatible
- Licencefree up to 3 developers
No benchmark figures yet. The evaluation baseline hasn't been recorded, so this page quotes no latency, quality or cost numbers.