Demiton Storage
The Demiton Storage adapter writes pipeline-generated artifacts - PDFs, reports, exported datasets, payment files - to Demiton’s Azure Blob Storage. It is provisioned automatically for every organisation; no connection setup is required.
Authentication: Platform-managed (managed identity)
System type: DEMITON_STORAGE
Supported resources
| Resource | PUSH |
|---|---|
artifacts | ✓ |
artifacts is the only resource. Each workflow run that produces file output pushes records here; the adapter detects binary content by finding keys ending in _base64, decodes them, and uploads each file individually.
Integration model
This connector is platform-managed - no tenant credentials are required or accepted. The adapter uses Demiton’s Azure Storage account via the blob_service singleton, which authenticates with managed identity.
Blob paths are organisation-scoped:
org_{org_id}/artifacts/{resource}/{uuid}_{filename}UUID prefixes prevent filename collisions across concurrent runs. If no filename is provided in the record, a random .bin name is generated.
A SHA-256 hash is computed over the raw bytes before upload and returned in the response manifest, allowing downstream steps to verify artifact integrity.
Simulation mode is supported - dry-run calls return a manifest describing what would be uploaded without touching storage.
Security
Access type: Platform-managed - write-only (artifact storage)
Artifacts are stored in Demiton’s Azure Blob Storage, encrypted at rest with AES-256. Access is scoped by organisation - one customer’s stored data is never accessible to another.
No external system credentials are involved. The platform’s managed identity governs all storage operations.
Next steps
- MCP Server - platform storage is used for workflow artefact handling
- SharePoint - primary document store for customer-controlled files
- Connect your operation - platform storage is included in your Connected deployment