New deployment

Onboarding an operator takes days and several people. Nothing here has to be finished in one sitting.

Start a new deployment

Steps 1 to 3. Everything below is fixed for the life of the deployment.

Steps 1 to 3 are one form because they are one decision. Operator, brand, market, jurisdiction, currency, timezone and locale are fixed for the life of the deployment — changing a currency is not an edit, it is a different deployment, and treating it as an edit would silently re-denominate money that has already been recorded.

Lowercase letters, digits and hyphens. Appears in URLs and in the standalone binding.
A starting point, not law. What matters most about a template is the list of things it refuses to decide.
ISO-3166, e.g. NG.
ISO-4217, three letters. Every figure on every screen is denominated in it.
An IANA name, e.g. America/Sao_Paulo. Deliberately not one of this installation's own markets: an example that named one would be the first place somebody copied the wrong value from.
A BCP-47 tag, e.g. pt-BR. Dates and numbers are formatted with it.
Created INVITED with a hash nobody holds the preimage of. A bootstrap token is issued once and is the only way in.

Templates

A starting point, not law. What matters most about each is the list of things it refuses to decide.

What creating a deployment does not do

  • It does not activate. The deployment and its configuration are both DRAFT, because a deployment that came up ACTIVE would be one nobody had configured reporting itself as running.
  • It does not choose an adapter. The sportsbook adapter is the literal string UNCONFIGURED, which fails validation loudly rather than failing silently at the first event.
  • It does not set a password. The first administrator is created INVITED with a hash nobody holds the preimage of, and the bootstrap token is printed once.
  • It does not seed platform administration into the operator’s roles. Provisioning deployments is Playtek’s job and stays there.