Two-sided matrix
Every working relationship rated from both ends. The gap is the finding.
A five-minute check-in each cycle that rates every working relationship from each end, shows how much of your effort reaches the people who judge the result, and asks whether everyone still means the same goal. Open source. Team-level only. No scores on people.
Free for one team on the hosted version. Self-hosted is free for everyone; companies that keep using it buy a one-time licence.
Health checks ask how the team feels. They don’t ask how the team looks from the manager’s seat, or from the client’s. The gap between those views is where most work goes wrong, and nothing you use today measures it.
Developers · Management · Stakeholder is one; a platform team and its consumers is another. Any set of roles works.
Sliders, not scores: how does the relationship look from where you sit? How much of your week reached the stakeholder? Do we still mean the same goal?
Each relationship rated from each end, and the gap between. A quadrant shows effort reaching the stakeholder against the value they say they got.
The AI reads the aggregates and writes questions, never verdicts. You decide what to do with them.
How well does your connection with Management work this cycle?
Can’t judge this one
No numbers while you drag, and “can’t judge” is always an answer. The stakeholder gets a 60-second form, no account.
Every working relationship rated from both ends. The gap is the finding.
How much of the team’s energy stays inside, and how much reaches the people who judge the result. Neither is good or bad; the trend is what matters.
Effort toward the stakeholder against the value the stakeholder reports. Watch the dot move from cycle to cycle.
Who asks whom for help. Team-visible, opt-in, hidden below five people.
Do developers, management and stakeholder still describe the same goal? Where do they want it changed?
After six sessions: is the team stable, shifting, or in a zone where small things decide the outcome?
A delivery team, its managers, and whoever judges the result.
Product teams whose owner sits in management.
A platform team and its consumers.
Small companies. Nobody outside judges.
AI agents, rated by the people using them.
◆ judges the result. Write your own preset →
Enforced in the server, not promised in a policy.
The whole product is Apache-2.0, presets included. Run it for as long as you like. If your company keeps using it, buy a one-time licence.
docker run -p 8080:8080 -v gyrator:/data ghcr.io/OWNER/gyratorUnlicensed copies work fully. They print one small line on reports and exports. That’s the entire enforcement:
Free for one team. $49 per team per month after that; $99 with AI retro questions, a portfolio view across teams and alerts. EU-hosted, SSO, backups, support. Export your data any time.
With the Stakeholder preset, the client answers a 60-second form each cycle and sees the pooled report. Renewals stop being a surprise.
Gyrator began as essays on how teams work as systems. The tool measures what they describe, and what the tool finds goes back into them.
No. It cannot produce a per-person result; the product refuses to.
Under five minutes per person per cycle; the stakeholder form under 90 seconds.
It works from two people; the cooperation network switches on at five.
A systems model of activity by A. N. Malyuta. The method is written up in full and updated as the tool changes; you don’t need it to use the tool.
Yes. Every preset is a YAML file, and there is a visual builder in setup.
No. It receives aggregates and anonymised free text.
There is a one-page explainer for German, Dutch and French consultation; the network feature is off by default.