Goal: Have a more seamless experience with self-service private hosting onboarding

Collaborators:

Rough Timeline: Q2

Strategic Questions

• Do we want to drive users from public to private hosting?
  • Pros: bigger contracts
  • Cons: harder to maintain, would potentially cannibalize the higher tiers of public hosting
• Do we want to continue offering the self-service path for local?
  • Pros: fast self-hosted competitor to TensorBoard and MLFlow
  • Cons: no clear path to monetization yet, not contributing to community, cannibalizing enterprise use of the multi-tenant cloud?
• Can we identify heuristics in the simple wandb local container to push company leads?
  • Ex: could we identify common git repos like microsoft that people are pointing to and then trigger some messaging in the Private Hosting UI to say “Hey time to get a real license if you’re doing professional work”

Design priorities

Onboarding + Setup

• Org name is confusing
  • Remove “Organization” question from the local deployer, and auto-create the unique id org in the backend. Use a
  • give us work email
    • if we’ve seen it before = drive you to join existing team
    • otherwise: tell us the name of your company
  • Use the plain text name of company in the UI to describe the organization, like “Carta’s Deployments”
• API to put your license in local automatically

Data Migration

• @Chris Van Pelt has previously talked about “The Great Migration” tool, which would allow you to take data from your hosted cloud install and move it to Private Hosting