Competios → For games
For games
Not built yet. Being built with one studio.
This is the page for a studio that wants tournaments and leaderboards inside its own game, run by somebody else. Every capability described below is something we are building, not something that exists to call today — there is no SDK, no endpoint and no dashboard behind this page, and we would rather say so than publish a gallery of integrations that do not exist.
What exists today
One accepted contract, and nothing else.
Being precise about this is the whole point of the page.
An execution contract, agreed with the first studio.
The shape of how an external system reports what happened in a match — the contract itself — is written and accepted, as one milestone of the Chess Raiders work. It is a document two teams agreed on, not a running endpoint.
- No public integration surface: no SDK, no client library, no sandbox, no keys to issue.
- No provider result-report endpoint. The only result route that ships is the organiser one, authenticated as a person rather than as a game server.
- No leaderboard of any kind, anywhere in the product.
- No embed and no widget: nothing to drop into your game’s UI.
- No provider-executed contest has run in production.
What we are building
The shape we are aiming at.
Written in the future tense because that is where all of it lives. If a line here matters to you, that is the most useful thing you can tell us.
You will report a result
Your game finishes a match and tells Competios who played and how it went. That is intended to be the whole integration — one call, from your backend, when a match ends.
We will own the competition
Pairings, stages, standings, progression and the correction path stay ours: the parts you would otherwise rebuild, and the parts that are already built and tested for organisers today.
You will read it back
Standings, brackets and leaderboards, returned in a shape you can render inside your own game so your players never leave it.
We will do it with one studio first
Chess Raiders is that studio. A path proven with one real game beats a published SDK nobody has used, and it is why this page offers a direct conversation rather than documentation.
A separate market
Organiser pricing is not an integration price.
The published offers are for founder-assisted real-world events. A studio integration carries engineering, security and support work that must be scoped and priced separately once the production integration surface exists.
There is no studio API, SDK, checkout or platform package to buy today. We will not use organiser prices to imply otherwise.
The way in
Is your game the second one?
Tell us what you run, how many people play it, and what you would want Competios to take off your hands. If we are years from fitting, we will say that.
Participants register on the public event page once you publish. Prefer a hand-held first night? Email us with the date, format and likely entrant count.
Start on Competios
The create form is the organiser front door. Published events still list Register for entrants at /events.
Create competitionOpens the Competios create form on this site.
Email about organisingUse your normal email account. You are not added to a mailing list or automated sales sequence.