type: a dotted string of the shape
<namespace>.<content kind>.<name>, chosen when the blob is created and fixed for its lifetime. The internal
data structure, storage semantics, and API commands for a blob depend entirely on that string.
Five type strings exist today:
Workflow
The Workflow Blob Type (blobhub.compute.workflow) is designed to build, manage, and execute complex backend workflows.
- You can treat memory and data as first-class citizens with built-in state management.
- Supports managing Definitions, initiating and monitoring Executions within Sessions, and accessing real-time Execution Events.
Scheduler
The Scheduler Blob Type (blobhub.compute.scheduler) stores a collection of schedules that trigger workflow executions on a time-based cadence.
- Supports both one-time and recurring cron schedules with full timezone control.
- Retains a history of past executions, including success and failure details for each firing.
ONNX
The ONNX Blob Type (blobhub.model.onnx) provides specialized hosting for Open Neural Network Exchange (ONNX) machine learning models.
- Provides commands to securely perform multipart uploads of the raw model files.
- You can describe the structure of an uploaded model archive or retrieve presigned download URLs for the components.
Graph
The Graph Blob Type (blobhub.graph.orientdb) backs general-purpose graph storage in a dedicated OrientDB
database. Not documented in depth here.
NLP Dataset
The NLP Dataset Blob Type (blobhub.dataset.nlp) stores NLP dataset content. It has no data-plane
commands of its own — a data/command or data/query call against it answers unsupported_operation — so
it is created and read through the platform’s shared primitives rather than through type-specific commands.
Not documented in depth here.