Management services¶
Management services form the control plane of the dataLOFT platform. The following table lists all management services, their implementation language, and their role.
| Service | Language | Role |
|---|---|---|
| RUN-DSP | Go | Core connector implementing the IDSA Dataspace Protocol. Handles catalogue queries, contract negotiation, and data transfer for both provider and consumer roles. |
| Signature-Auth-Handler | TypeScript (NestJS) | Validates DPoP tokens, resolves did:web documents, and verifies that the requesting participant is registered in FC-Service. |
| HST-DID | TypeScript (NestJS) | Hosts did:web documents for dataLOFT participants. |
| Reference Contract Service | Go | Reference implementation managing contract state transitions for RUN-DSP. |
| FC-Service | Java/TypeScript | Gaia-X-compliant federated catalogue. Stores participant self-descriptions and service offerings. |
| Consent Management App (CMA) | Flutter / Go | Application for consent management by data owners. Described in conceptual terms; the implementation is subject to redesign. |
| rdsp-s3 | Rust | Reference provider backend. Serves file metadata and download URLs from an S3-compatible object store via the run-dsrpc gRPC interface. |
Each service is documented in detail on its own page:
- RUN-DSP
- Auth subsystem (Signature-Auth-Handler + HST-DID)
- FC-Service
- Consent Management App
- Reference Contract Service
- rdsp-s3