Skip to content

Epic: per-tenant namespace isolation and fast teardown (SDK-native) #555

Description

@somfornot

Design: #554 (docs/explanation/tenant-namespace-isolation.md).

Per-tenant data namespace isolation + fast tenant-offline teardown on the SDK-native direct data plane. Tenant = the SDK-declared TenantId, treated as a trusted partition key; each tenant has a private namespace backed by its own origin bucket + credentials (coordinator-distributed registry). The object-store gateway is out of scope.

Decisions (locked)

  1. Boundary = SDK-declared TenantID, trusted partition — not bucket/prefix, not a gateway principal; not a hard security boundary (native-plane auth is an additive follow-on).
  2. Private per-tenant namespace — same path → different data per tenant; tenant participates in origin addressing.
  3. Per-tenant origin — each tenant has its own bucket + credentials via a coordinator-distributed registry.

Delivery slices

Note: the design (#554) is under review; slices may adjust.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions