About Greenroom
Built by people who have stayed up counting.
Greenroom exists so no organizer has to choose between finishing on time and getting it right.
Origin
Why we started
Greenroom started in a hall at two in the morning, with four people, a stack of score sheets and a calculator. The results were due at nine. Everything about that night was avoidable.
Cultural festivals here are run by institutions, not software teams. A madrasa, a school, a college. The programmes are complex, the judging is genuinely subjective, and the person coordinating it all is usually a teacher with a day job. The tooling they get is a spreadsheet and goodwill.
So we built the thing that should have existed: one system that holds the participants, the programmes, the stages, the judges and the scoring rules — and turns a judge pressing save into a published, defensible result.
What we stand for
Four rules we build against
- 01
Every number has a paper trail
Each score, edit and publish action is written to an audit log with the actor and the time. If a result is questioned, the answer is in the system rather than in someone's memory.
- 02
The festival cannot wait for us
A festival happens on one weekend and never again. The dashboard, the judge portal and the public site are built to hold up on the day, on hall wifi, on whatever device someone brought.
- 03
Organizers should not need training
The people running these events are volunteers and teachers. If a screen needs explaining, that is our bug, not theirs.
- 04
The public site is part of the product
Results are not an internal artefact. Participants, parents and rival teams all read them — so they get a real site, in the festival's own colours, updated the moment results are published.
“Simplify festival operations so organizers can focus on the art, and judges can focus on the talent.”