Workflow / orchestration
When and in what order should work happen?
Scheduling and coordinating workflows
Positioning
What problem does Platform solve?
DrToller.Framework is the workload and runtime.DrToller.Platform is the deployment environment. Infrastructure is how that environment is implemented. Workflow orchestration answers a different question and can sit beside both.
Framework defines the workload. Platform supplies the environment.
Developer preview · August 2026. Abstraction layers, not a product ranking.
The problem
A workload runtime still needs an environment in which to operate. Platform is that layer, so the execution contract and domain steps stay independent of how the environment is installed.
The abstraction
Composition
workflow / orchestration
+
Framework
+
Platform
+
infrastructureEnvironment model
Workload
↓
Framework
↓
required capabilities
↓
Platform
↓
environment implementation
↓
infrastructureThese layers compose. A reference environment is a starting point, not a requirement.
How the abstraction differs
Different questions, often in one installation.
DrToller.Framework
What is the workload, and how does it execute?
Workload definition and runtime semantics
DrToller.Platform
What environment provides the runtime?
Deployment environment: provisioning, wiring, lifecycle, health
Infrastructure
What concretely implements that environment?
Environment implementation — chosen per deployment
Layer table
| Layer | Question |
|---|---|
| Workflow / orchestration | When and in what order should work happen? |
| DrToller.Framework | What is the workload, and how does it execute? |
| DrToller.Platform | What environment provides the runtime? |
| Infrastructure | What concretely implements that environment? |
Layer detail
Orchestration
When and in what order
Workflow systems such as Airflow, Dagster, or Prefect schedule and coordinate work. That is a different question from what Platform answers. They can coexist: an orchestrator can invoke a Framework workload that runs in a Platform environment.
Runtime
DrToller.Framework
Framework is the workload and runtime: DRTML, processing, algorithms, metrics, storage and parallelism contracts. Platform hosts that runtime; it does not replace it.
Environment
DrToller.Platform
Platform provides the deployment environment in which the runtime operates: provisioning, wiring, lifecycle, health, and operational configuration. Required capabilities are bound to that environment. How they are implemented is not the definition of Platform.
Infrastructure
Environment implementation
Infrastructure is the concrete realization of an environment. You can use a shipped reference, change parts of it, or provide a different implementation. The intended model is that the workload stays the same when the implementation changes.
Reference impl
Current reference — examples only
Today’s self-hosted reference environment uses Compose on a VM, an operator CLI, and optional KubeRay attach on an existing DOKS cluster. A workflow host in that reference can passstep_id and params into Framework. Those names are examples of the current reference, not Platform requirements.
AWS/EKS and GCP/GKE installers are backlog. A pack marketplace is not implemented. Platform is OSS and self-hosted.
What to evaluate
What Platform provides
The deployment environment for a Framework workload: bootstrap, wiring, lifecycle, health, and operational configuration bound to Framework contracts.
Capabilities before products
The environment is specified by required capabilities. A reference environment fills those slots with particular systems. Those systems are not the definition of Platform.
Reference vs abstraction
Platform is the layer. Under it: reference environments, customizations, and user-defined environments. A shipped reference is a starting point, not a requirement.
Current vs intent
A self-hosted reference environment exists today. Additional cloud installers and a managed offering are backlog. Keeping the workload stable across environment implementations is the intent, not a completed substitution product.
Where work lives
Platform: deployment environment — provisioning, wiring, lifecycle, health. Framework: workload and runtime. Domain steps live in separate packages — for example the OSS pack DrToller.Edge. Semantic Layer: ontology and semantic APIs (separate product).
Domain logic step packages
Workload / runtime Framework
Environment Platform
Implementation infrastructure