Platform
Everything in this section is shared across Invokation products. A single sign-up covers all of them: the same organisation, portal, and credentials apply to IVK Match and to any service added later.
Organisations and games
Section titled “Organisations and games”Tenancy has two levels.
An organisation is the ownership and billing boundary. It holds team members, the billing relationship, and one or more games.
A game (or app) is the unit of tenancy for the services themselves. It holds queues, credentials, and usage records. Isolation is per game: nothing is shared between two games, and nothing is shared between two organisations.
Most teams start with one organisation and one game, and add games as they ship titles. Sign up for a free-tier organisation to get started; no contract or sales conversation is needed to build an integration.
The portal
Section titled “The portal”The portal is for administering an organisation and its games without going through an API:
- Create the organisation and invite team members.
- Create a game and issue, rotate, and revoke its API credentials.
- Author and edit queue configuration, and see what is currently live.
- Watch usage against the plan.
Configuration made in the portal takes effect on the running service; no deploy step is needed on the game’s side. See Queue Configuration for what a queue declares.
Credentials
Section titled “Credentials”Credentials are issued per game from the portal and belong in the game backend’s secret store. They authenticate the backend to the API, so they must never ship in a game client, where anyone can extract them and act on the game’s queues.
See Authentication for how to attach them to a call.
Where things run
Section titled “Where things run”Invokation operates the service; there is nothing for the game team to run. The game backend talks to a hosted endpoint over TLS. Nothing in the product documentation assumes access to a container, a filesystem, or a message broker.