A tool for the person who runs the thing.

Why this exists

Pairings, standings and progression are a solved problem that nearly everybody re-solves badly, by hand, once a week. The interesting part is never the maths — it is that the state has to stay right while ten people touch it, results arrive out of order, and somebody has to be able to fix a mistake without erasing the record of it.

So the engine came first: an immutable result log, a real adjudication path, idempotent writes and version fences. The screens are coming after, which is an unusual order and the reason this site is careful about what it claims.

Where we are

The offline organiser loop is in production and tested: enrolment, bracket generation with honest byes, result entry, standings, adjudication, and a public page that needs no account. It is driven through an authenticated HTTP API, documented in a runbook, with no organiser screen yet.

That means a competition is set up for you rather than by you, and during the pilot we do it alongside the organiser. It also means we would rather have five organisers we talk to every week than five hundred sign-ups we cannot support.

Who we are

Competios is built by Sneat Co., which builds a small family of products in the open. The person who reads your message is the person who writes the code.