Feature
Pluggable Runtimes
Agents run through a framework-agnostic Runtime port, picked per Agent, with no silent fallback to a billed Runtime.
The Runtime is chosen per Agent, on both direct Invoke and every Process Step. openai and claude-mcp call the model providers’ APIs; noop is a first-class do-nothing Runtime and is never swapped for a billed one. An unknown Runtime fails the Agent run.
A model that contradicts the Runtime is rejected before any call, so it spends nothing. Every call is bounded by a maximum token count.
vercel-ai, semantic-kernel and langgraph are registered as unsupported: choosing one fails cleanly with a not-implemented error. Container Runtimes for AWS ECS and Azure Container Apps jobs exist as a seam and stay unsupported until adapters are configured; running agents across clouds is on the roadmap, not shipped.
Agent runs left running past their Runtime’s stale window are marked failed by the Reaper, and recorded as such rather than retried.
More features
All features →- 01
Application lifecycle
Create, configure and delete Applications with Quotas per Cluster, Namespaces, Ownership links and Extended resources.
- 02
Pipelines and Pipeline runs
Record the CI/CD definition of each Application and every execution of it, with Commit statuses beside them.
- 03
Deployment tracking
Follow each Deployment of an Application on a Cluster, with service type, DNS, Stages and Events.