DrToller

DrToller.Platform

The deployment and operations layer for DrToller workloads.

DrToller.Platform provides an environment capable of running aDrToller.Framework workload. Framework is the workload and runtime. Platform is the deployment environment. Infrastructure is how that environment is implemented.

Workload
      ↓
Framework
      ↓
required capabilities
      ↓
Platform
      ↓
environment implementation
      ↓
infrastructure
01

Environment

The environment a DrToller workload runs in

A DRTML workload describes what to execute. Framework defines runtime semantics. Platform is the deployment and operations layer: it provides an environment capable of running that workload — provisioning, wiring, lifecycle, health, and operational configuration.

02

Contracts

Capabilities and contracts

An environment is specified by what the runtime needs: object storage, persistence, distributed execution, orchestration hooks, observability, and related services. Platform binds Framework contracts to those capabilities. How each capability is implemented is an environment choice.

03

Reference

Reference environments

Platform is the abstraction. Under it sit reference environments, customizations, and user-defined environments. DrToller ships a self-hosted reference as a starting point. You may run it, change it, or provide a different one. A reference is an example of Platform, not the definition.

04

Operate

Bring-up, wiring, and health

For a given environment, Platform covers bootstrap, service wiring, secrets and host paths, lifecycle, and health checks. Operator docs stay with Framework deploy pages so the runtime contract and the environment remain one reference.

05

Choice

Use, modify, or build your own

You can use a reference environment, replace individual parts, combine pieces, or wire an environment yourself. The intended model is that the DRTML workload stays the same when the environment implementation changes. Sharing environments in a community is an architectural possibility — not a shipped registry or pack format.

06

Reference impl

What ships today

The current self-hosted reference environment uses Compose on a VM, an operator CLI, and optional KubeRay attach on an existing DOKS cluster. Those names are implementation choices, not Platform requirements. AWS/EKS and GCP/GKE installers are backlog. A managed offering is compatible with the model and is not a product today.