One Workspace per Firm, with a Private Bucket

Each client firm gets one workspace on our server holding all its deals, plus a private bucket of its own for originals and backups.

Path
decisions/One-Workspace-Per-Firm-With-a-Private-Bucket.md
Authors
Michael Staton
Augmented with
Claude Code on Claude Opus 5.5 (1M context)
Tags
Decision · MemoPop · Multi-Tenancy · Object-Storage

One Workspace per Firm, with a Private Bucket

The decision

  • One workspace per client firm, holding all of that firm’s deals. This is the shape io/<firm>/deals/<deal>/ already has. Everyone the firm brings in sees all of its deals; per-deal access can be added inside a workspace later.
  • The server disk is canonical. The workspace sits on the server’s volume exactly as the code expects it, so nothing has to be rewritten to run hosted.
  • Each firm gets its own private bucket. It holds the original materials (decks, datarooms, PDFs, images) and every backup snapshot. Provisioned by hand at first, automatically once didi.sh takes payments.

Decided 2026-10-10 by Michael Staton.

Why

  • It matches the code and the data we already have. Eleven firms already live as io/<firm>/, and the orchestrator reads that layout directly.
  • A firm’s data stays separable. One bucket per firm means a client’s files can be handed over, exported, or deleted without touching anyone else’s.
  • A firm, not a deal, is who signs up. The firm is a didi.sh entity, and the sign-in token names it.
  • [[MemoPop-as-a-Claude-Connector]] — the exploration this came from
  • [[jj-Versions-Text-and-Saves-Snapshot-to-the-Bucket]] — what goes in the bucket and when
  • [[A-Syncbox-For-Client-Document-Folders]] — the storage reasoning this reuses