Back to Studio
Studio use cases

Choose the workspace path before you touch live operations.

Hosts, providers, promoters, and operators use different Studio surfaces. This page maps each role to the current tools, live plan catalog, and gates that still need real records or owner credentials before launch claims are valid.

Live public signals

Plan tiers

4

Loaded from the public plan catalog at request time.

Public events

0

Zero is an honest empty state, not a seeded demo feed.

Public services

0

Provider marketplace proof still requires real listings.

Hosts

Publish an event and run the door

For crews that own the event listing, ticket tiers, capacity, scanner, refunds, and post-event galleries.

Entry
$29.00 / month entry
Fee
Standard checkout fee

What this path covers

  • Create draft or published event records in Studio.
  • Add ticket types from the event workspace.
  • Use the scanner and refund tools after real orders exist.

Gate: Live checkout, Tax/Radar, webhooks, and real order QA still require owner-controlled Stripe setup.

Start host setup

Service providers

List services that hosts can book

For DJs, photographers, security, production, and event managers who need a discoverable provider workspace.

Entry
$29.00 / month entry
Fee
Standard checkout fee

What this path covers

  • Create a provider workspace with a service specialty.
  • Publish provider-owned service listings.
  • Track bookings and payout readiness from Studio.

Gate: Public listings, destination charges, and payout proof stay partial until an operator-owned provider record is verified.

Set up provider workspace

Promoters

Request collaborations and track attribution

For people bringing an audience to an event while the host keeps control of the listing and settlement decisions.

Entry
Role-based
Fee
No public plan required

What this path covers

  • Create a promoter workspace separate from host operations.
  • Request event collaborations from the promoter tools.
  • Track accepted collaboration status and projected earnings.

Gate: Attribution and projected earnings are not settled payouts; real revenue-share behavior needs role-based QA.

Start promoter setup

Operators

Check readiness before calling the platform live

For admins and launch reviewers who need source, build, runtime, browser, data, and gate evidence in one place.

Entry
Role-based
Fee
No public plan required

What this path covers

  • Review public endpoint health and inventory counts.
  • Compare live plan tiers and activation boundaries.
  • Keep gated launch work visible before owner sign-off.

Gate: Admin routes require an authorized super-admin account; public status does not prove private role flows by itself.

Open readiness status