BetPulseTenant Studio

Tenant Studio

Where an operator shapes how their brand looks: theme, layout and the content on each page, previewed before it goes live.

Scaffolded, not built

This application exists so that pipelines (build, test, deploy) can be set up alongside the sportsbook and the operator portal. It runs, it builds, it has a test suite. It does not yet edit anything.

What has to exist first

  • A page-composition model. Home-page blocks are hard-coded in the sportsbook today. A studio that arranges blocks needs blocks as data, and a renderer that reads them.
  • Design tokens that actually drive both front ends. A brand publishes one colour today. A theme editor needs the token set to be real before it has anything to edit.
  • A draft state on brand configuration. Configuration is versioned and publishes atomically, but there is no unpublished draft, so there is nothing for a sandboxed preview to render that is not already live.
  • Somewhere to put media. Content references URLs an operator hosts. The first thing anyone does in a studio is upload a logo.
  • Manageable roles. A studio is where an operator hands access to an agency, which is the point at which hand-edited realm roles stop being acceptable.

Tracked as backlog items 41, 48, 49 and 52 in docs/planning/backlog.md.