# Delivery Intelligence & Orchestration Overview

OpsMx ISD for Spinnaker is an Intelligent Software Delivery (ISD) platform built on top of Spinnaker to provide secure, scalable, and enterprise-grade continuous delivery across multi-cloud and Kubernetes environments. It enhances open-source Spinnaker with additional capabilities such as security governance, deployment intelligence, policy enforcement, automated verification, observability, and risk analysis.

The platform is designed to automate software delivery while minimizing human intervention and deployment risk. It combines orchestration, intelligence, visibility, compliance, and security into a single continuous delivery solution.

OpsMx ISD primarily consists of two major modules:

* **OpsMx Enterprise for Spinnaker (OES)** – orchestration and deployment automation
* **OpsMx Autopilot** – intelligence, verification, governance, and policy enforcement

## Why we use it in OpsMx

OpsMx uses ISD for Spinnaker to provide secure, intelligent, and automated software delivery for enterprise environments where scalability, compliance, governance, and deployment reliability are critical.

### Key reasons for using ISD for Spinnaker

#### Secure continuous delivery

ISD helps organizations implement DevSecOps practices directly into CI/CD pipelines by integrating security checks, governance rules, vulnerability scanning, and policy enforcement into the deployment process.

#### Intelligent deployment automation

OpsMx automates deployment approvals and verification using AI/ML-driven analysis of logs, metrics, tests, and deployment data. This reduces manual intervention and minimizes deployment risks.

#### Multi-cloud and Kubernetes delivery

ISD leverages Spinnaker’s orchestration capabilities to deploy applications consistently across Kubernetes, public cloud, hybrid cloud, and on-premises environments.

#### Policy-driven governance

The platform allows enterprises to define deployment rules, security guardrails, blackout windows, approval workflows, and compliance checks directly within deployment pipelines.

#### Risk reduction and deployment safety

OpsMx uses automated risk scoring and continuous verification to detect anomalies, performance degradation, and vulnerabilities before production deployment.

#### Enterprise observability and visibility

ISD provides centralized dashboards, deployment insights, DORA metrics, audit trails, and operational intelligence across CI/CD workflows and microservices.

## How we use it in OpsMx

OpsMx uses ISD for Spinnaker to automate secure software delivery pipelines, manage multi-cloud deployments, enforce governance, and improve deployment reliability across enterprise software environments.

### Continuous delivery orchestration

OpsMx uses Spinnaker-based orchestration to automate:

* Application deployment workflows
* CI/CD pipeline execution
* Multi-cluster Kubernetes deployments
* Hybrid and multi-cloud releases
* Canary and blue-green deployment strategies
* Automated rollback mechanisms
* Pipeline-as-code workflows

This allows development teams to release software faster and more consistently.

### Security and governance enforcement

OpsMx integrates security and governance checks directly into deployment pipelines using:

* Deployment firewalls
* Policy-based approvals
* Security vulnerability scanning
* Compliance checks
* Blackout window enforcement
* Audit reporting
* Role-based access controls

This ensures software releases meet enterprise security and compliance requirements before production deployment.

### Automated risk verification

OpsMx Autopilot continuously analyzes:

* Logs
* Metrics
* Test results
* Security scans
* Deployment telemetry

Using AI/ML models and anomaly detection, the platform calculates deployment risk scores for:

* Performance
* Reliability
* Quality
* Security

This helps teams identify release risks early and avoid production failures.

### Visibility and delivery intelligence

OpsMx provides centralized visibility into software delivery processes through:

* Application dashboards
* Pipeline monitoring
* Deployment tracking
* DORA metrics
* Audit trails
* Failure analysis
* Infrastructure health monitoring

Teams can monitor deployments, investigate failures, and optimize release performance from a single platform.

### GitOps and self-service delivery

OpsMx supports GitOps-based delivery models and self-service onboarding capabilities, enabling teams to:

* Manage pipelines as code
* Integrate with Git repositories
* Reuse deployment templates
* Enable decentralized team workflows
* Scale CI/CD processes efficiently

This improves developer productivity and operational scalability.

## Core capabilities of ISD for Spinnaker

| Capability              | Description                                              |
| ----------------------- | -------------------------------------------------------- |
| Multi-cloud deployments | Deploy across Kubernetes, cloud, and hybrid environments |
| Continuous verification | AI/ML-based deployment validation and anomaly detection  |
| Policy enforcement      | Security, governance, and compliance checks              |
| Deployment strategies   | Canary, blue-green, and automated rollback support       |
| Visibility and insights | Centralized dashboards, DORA metrics, and audit trails   |
| GitOps support          | Pipeline-as-code and Git-based workflows                 |
| DevSecOps integration   | Security integrated into CI/CD pipelines                 |
| 70+ integrations        | Integration with major CI/CD and DevOps tools            |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opsmx.com/delivery-intelligence-and-orchestration/delivery-intelligence-and-orchestration-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
