Deployment Guide
ENSUC products deploy entirely inside your environment. There is no cloud dependency, no external telemetry, and no vendor access to your data or workloads. Deployment is designed to be reversible at every step.
Deployment Modes
Shadow
Observes your existing scheduler and reports what it would have done differently. Zero risk. No scheduling decisions are enforced. Used for evaluation.
Plugin
Runs alongside your host scheduler and intervenes only when it can make a strictly better decision. Incremental adoption.
Standalone
Operates as the primary scheduler for the cluster, with full capability enabled.
Requirements
- A supported container orchestration environment
- Standard cluster access credentials scoped to scheduling operations
- Outbound network access is not required (air-gap supported)
- Resource footprint is minimal and runs on existing infrastructure
Installation Flow
- Deploy in Shadow mode
- Observe against live workload for an evaluation window
- Review the comparison report with your account team
- Promote to Plugin or Standalone when ready
Rollout Path
Most organizations begin in Shadow mode, validate against their own workload, then advance at their own pace. There is no forced cutover. Rollback to a prior mode is immediate.
Support
Deployment is supported directly by our engineering team. Regulated and classified environments are supported with on-site or air-gapped installation procedures.
Continue the conversation
Need the full technical context?
Request the full deployment runbook under NDA.
Request access