Skip to main content
When you first sign up for sureops, you choose how you want to get started. There are two paths, and they lead to the same product — the difference is what sureops is connected to.

Demo environment

sureops provisions a sample application with real observability data, pre-wired telemetry, alerts, and a Slack war-room. You trigger a failure and watch agents respond — no infrastructure required.

Adopt (your stack)

You connect sureops to your own services, telemetry, GitHub, and Slack. Agents respond to real incidents in your environment from day one.

​
Demo environment

The demo environment is a fully provisioned sample application — a realistic microservices stack instrumented with OpenTelemetry. sureops provisions it for you during onboarding; you do not need to bring any infrastructure. What comes pre-wired:
  • A running sample application with traces, metrics, and logs flowing into sureops
  • Alert rules that fire when the application degrades
  • A dedicated Slack war-room channel
  • A GitHub fork of the sample app where agents open fix PRs
  • A managed AI model — no API key required
The demo environment is designed to let you experience the full incident lifecycle in about 10 minutes:
  1. Trigger a real failure from the onboarding wizard
  2. Watch the Incident Commander detect and triage it
  3. Review the Diagnosis Specialist’s root-cause analysis
  4. Approve (or reject) the proposed fix
  5. Watch the Resolution Specialist execute it
  6. Confirm recovery via metric verification
The demo environment is a real application running real code. The failures you inject are genuine — agents diagnose them from live telemetry, not from scripts. This is the same response loop your agents will run against your production environment when you adopt.

​
When to use the demo path

  • You want to evaluate sureops before committing to an integration effort
  • You want to show sureops to colleagues or stakeholders with minimal setup
  • You want to understand the full incident lifecycle before connecting your own stack

​
Adopt (your own infrastructure)

The adopt path connects sureops to your real services. Once connected, sureops agents respond to incidents in your actual environment — diagnosing from your telemetry, proposing fixes as PRs in your repos, and posting to your Slack channels. What you bring:
  • Your services, instrumented with OpenTelemetry (or behind a Grafana/Prometheus proxy)
  • A GitHub organization where sureops can read repos and open fix PRs
  • Slack for incident war-rooms
  • Your alerting system (Alertmanager or any webhook-capable alert source)
The five-step connection process is covered in Connect your stack.

​
When to use the adopt path

  • You are ready to connect real infrastructure
  • You have OTel-instrumented services in Kubernetes or elsewhere
  • You want agents responding to real incidents from day one

​
Can I switch between paths?

Yes. You can run a demo environment and an adopt environment under the same organization simultaneously. Many teams start with the demo to get familiar with the interface, then set up an adopt environment for a non-production cluster before eventually connecting production. Environments are independent — separate telemetry connections, separate incident histories, separate agent configurations. Use the context switcher in the sidebar to move between them.

​
What is NOT different between paths

Everything in the sureops interface works the same way regardless of which environment type you use:
  • The Command Center, Incidents, Problems, Analytics, and Chat pages all work identically
  • Agent behavior is identical — the same Incident Commander, Diagnosis Specialist, Resolution Specialist, and Verification Specialist agents run in both
  • HITL approvals, control modes, and escalation routing work the same way
  • Your AI model settings and agent configuration apply per-environment
The only difference is what the agents are connected to.