Multi-tenancy¶
Single instance, multiple participants¶
A single RUN-DSP deployment serves multiple participants simultaneously. There is no requirement to run one connector instance per user or per organisation. This is a fundamental design goal of RUN-DSP and a key reason the platform was built as a custom connector rather than adopting EDC (see ADR-001).
Participant isolation¶
Isolation between participants is enforced at the contract and authentication levels:
- Each contract negotiation is scoped to a specific consumer-provider pair identified by their
did:webURIs. - The authentication hook verifies the identity of every request. A participant can only act within their own contract negotiations.
- The contract service hook can enforce additional policy constraints per participant or per dataset.
No process-level isolation is required. The connector handles concurrency internally.