10 minutes

Quick Start Guide

Experience OpsOrch as an operations control plane by visualizing your entire stack and seeing unified, correlated data.

✓ No production credentials needed✓ Runs entirely locally✓ Uses mock adapters

What you’ll do

1Start OpsOrch locally
2Open the Console
3Explore your infrastructure
4See correlated data

This is the smallest action that shows why OpsOrch exists.

Prerequisites

30 seconds

You need:

Docker
Container runtime
Docker Compose
Multi-container orchestration

Nothing else.

1Start the OpsOrch stack

3 minutes

Download the docker-compose file and start the local stack with mock adapters:

bash
curl -O https://raw.githubusercontent.com/OpsOrch/.github/main/profile/docker-compose.yml
docker compose up -d

This starts:

  • • OpsOrch Core (control plane)
  • • OpsOrch MCP server
  • • OpsOrch Console
  • • Mock providers for incidents, metrics, logs, tickets, and services

Wait until all containers are healthy.

2Open the Console

30 seconds

Open your browser:

URL:http://localhost:3000

You should see the OpsOrch Console with seeded operational data.

At this point, nothing magical has happened yet. That’s intentional.

3Explore your infrastructure

2 minutes

Navigate to the Services or Deployments views.

You will immediately see all correlated operational data in one place:

Related Tickets and Incidents
Relevant Logs and Metrics
Recent CI/CD Deployments

No queries required. OpsOrch automatically correlates this context for you.

4Observe what’s different

2 minutes

Notice the following:

Results come back typed, not free-form
Structured data you can act on, not just text
Data is correlated across systems, not siloed
Incidents, services, metrics, and logs connected
Evidence links point back to the original tools
No data copying, just intelligent routing
Shareable deep links preserve filters
Copy URLs to share the exact operational view
No data was copied or re-stored
Live queries to your actual systems
No direct access to vendor APIs was required
Safe, controlled interactions through adapters

You are not looking at a dashboard. You are interacting with a control plane.

This is OpsOrch’s core idea.

What just happened

You did not replace any tools. You did not sync data into a new system. You did not grant broad credentials to an AI.

Instead:

OpsOrch reasoned across operational systems
Actions and queries flowed through typed contracts
Control stayed with the operator

This is what "operations as a substrate" feels like in practice.

What to try next

If you want to go one step further:

Explore how actions require explicit execution
Inspect the MCP tools exposed by OpsOrch
Replace a mock adapter with a real provider
Connect an AI agent via MCP

But none of that is required to understand the core value.

Where to go from here

Architecture Overview
Understand how OpsOrch works
Provider Adapters
Connect your real systems
Demo Video
Watch the full walkthrough
Real Workflow
Integrate into production
AI Integration
Connect agents via MCP
Community
Join other operators

Or stop here.

If this page made sense, OpsOrch is likely relevant to how you think about operations.