Enterprise deployment
Your environment.
Explicit boundaries.
Understand where the system runs, how actions are authorised, and what your team owns before deployment.
Discuss your deploymentSteadyState deployment model
Control starts
with architecture.
SteadyState supports customer-managed Kubernetes deployment, with an AKS deployment kit and Docker Compose for local evaluation.
Explore SteadyState →- Identity and access
- Microsoft Entra ID sign-in and group-based roles connect access to your identity setup.
- Execution authority
- Policy checks, required approvals, dry runs, change freezes, and kill switches constrain actions.
- Audit evidence
- Hash-chained audit records and agent traces support investigation and review.
- AI provider boundary
- Optional AI features use your configured provider and credentials. Prompts may leave your cluster for that provider. Review the data path as part of deployment.
Define ownership together.
Your infrastructure
Agree who operates the cluster, network, secrets, backups, and identity lifecycle.
Your workflows
Scope integrations, allowed actions, approval owners, and the evidence retained for each workflow.
Your engagement
Document deployment assistance, support hours, escalation contacts, and response commitments in the agreement.