Guided onboarding journey

When you sign up for sureops, the guided onboarding journey walks you through everything you need to get your first incident running. The tour has 13 steps. Once your environment is provisioned, clicking through the tour itself takes about 10 minutes on the demo path — provisioning is a separate wait (see Step 3 below) and isn’t part of that estimate. The adopt path takes longer depending on how much of your infrastructure is already instrumented. You can skip most steps and resume from Settings → Onboarding at any time. ECHO guides you through each step with context-specific copy. One skip has a real consequence: skipping the GitHub username step (Step 8) silently enables auto-merge for agent-opened pull requests — see that step below.

​

Demo path vs. adopt path

Steps 1–3 are shared by everyone. From step 4 onward, the experience splits:

• Demo path — sureops has already provisioned the integrations for your sample environment. Most steps are “acknowledge and continue” rather than requiring you to configure anything.
• Adopt path — most steps are a confirm-and-continue button today, not an on-page configuration form — the tour doesn’t yet collect fields inline. The actual connection happens on the corresponding Settings page (linked from each step below); you do that first, then come back and advance the tour step to mark it done.

​

The 13 steps

​

Step 1 — Welcome to sureops

ECHO introduces itself and gives you an overview of what the tour covers. You can begin setup or skip the welcome screen.

​

Step 2 — Confirm your organization

Your organization name was pre-filled from your signup. This is the workspace your team shares — all incidents, problem records, and escalations belong to it. Confirm or change the name before continuing. You can update it later from Settings → Organization.

​

Step 3 — Your environment

An environment is what sureops watches. Every integration you connect, every incident that fires, and every agent action happens in the context of an environment.

• Demo path — click Provision sample environment to have sureops spin up your pre-configured sample app. This can take several minutes — sometimes longer — since it’s standing up a real running stack, not a mock. We’ll email you when it’s ready, so feel free to step away.
• Adopt path — create your environment in Settings → Organization → Environments → New environment (give it a name like production or staging), then come back and click Create environment here to mark this step complete.

This step cannot be skipped — all downstream steps are scoped to the environment created here.

​

Step 4 — Your AI model

sureops agents need an AI model to diagnose incidents, draft runbooks, and propose code fixes.

• Demo path — the AI model is already configured for your demo environment under sureops’s managed boundary. No API key needed. Click Continue.
• Adopt path — add your API key in Settings → Environment → AI Agents, then come back and click Save API key here to mark this step complete. Without a working AI model, agents cannot diagnose incidents or propose fixes. You can also skip this step and set the key later, but agents will not function until it is set.

​

Step 5 — Connect your telemetry

Telemetry is how sureops sees what is happening in your environment.

• Demo path — telemetry is already flowing from your sample application via OpenTelemetry. Traces, metrics, and logs are wired to sureops during provisioning. Click Continue to acknowledge.
• Adopt path — connect Prometheus or Grafana. See Connect your stack for the full setup guide.

​

Step 6 — Connect your alert source

Incidents come from alerts. sureops listens to your existing alerting tool and does not replace it.

• Demo path — your sample app’s Alertmanager is already wired to sureops via webhook. When thresholds breach, an incident opens automatically. Click Continue.
• Adopt path — there’s no self-serve alert-routing setup in the tour yet. Tell your sureops onboarding contact which alert source you use; they’ll set up the webhook registration on your environment.

​

Step 7 — Join your war-room (Slack)

When an incident fires, sureops creates a Slack channel automatically and posts agent updates, recommendations, and approval requests there.

• Demo path — a Slack channel was created for your sample environment during provisioning. Join it to watch ECHO post when an incident fires.
• Adopt path — authorize the sureops Slack app on your workspace.

​

Step 8 — Connect GitHub

GitHub enables two things: sureops reads your service contract from your KB repo, and the resolution agent opens draft fix PRs when it proposes code-level fixes.

• Demo path — a fork of the sample app was created for your demo, along with a separate docs/runbooks repo agents read from during diagnosis. Accept the GitHub collaborator invite to view the fork where agents open fix PRs.
• Adopt path — install the sureops GitHub App on your org and tag the repos you want sureops to access with the sureops-service topic.

This step asks for your GitHub username. Skipping it has a real consequence: without a username on file, your organization’s github_auto_merge setting is silently enabled, and agent-opened fix PRs get auto-merged without a human reviewer attached. If you want fix PRs to stay as drafts for manual review, provide your GitHub username here rather than skipping.

​

Step 9 — Generate your contract

The service contract is the source of truth for your service catalog — service names, owners, dependencies, runbook paths. Agents read it before every incident to understand blast radius and who to involve. Click Generate contract to have sureops read your observed services and open a draft PR with a pre-filled .sureops/services.yaml. Review it, edit anything sureops got wrong (especially ownership and runbook paths), and merge the PR. You can also hand-author the contract directly.

​

Step 10 — Discover your landscape

sureops cross-references your service contract with what is actually running in your environment. The result is a service map showing every service, its dependencies, and its deployment state. Click Generate landscape to run the discovery scan. The resulting service graph is what agents query when tracing blast radius and upstream dependencies during an incident.

​

Step 11 — Generate your runbook

Runbooks are operational playbooks per service — agents read them during diagnosis to know what to check and what fixes are pre-approved. Click Generate runbook to have sureops draft a runbook for your most critical service and open it as a PR. An empty runbook is better than no runbook — even a skeleton with headings tells the agent where to look.

​

Step 12 — Set up routing and escalation

When an incident fires, sureops requests HITL approval before running risky actions. This step is meant to let you configure the default approval behavior for unattended requests — what happens if nobody responds to a P1 approval in time — but that isn’t wired up yet. Per-user Slack routing, backup-approver escalation timeouts, and the default-behavior setting itself are all on the roadmap but not available yet — today this step doesn’t configure anything at all: there’s no destination it saves to. It exists as a placeholder acknowledgment in the tour ahead of that functionality shipping.

• Demo path — click Use defaults to move past this step.
• Adopt path — click Save routing to move past this step. Nothing you’d configure here is wired up yet.

​

Step 13 — Trigger your first incident

This is the payoff step. Pick a failure scenario and sureops injects it into your sample app — agents detect the degradation from live telemetry within a few minutes, then work the incident from alert to closure. Click Inject failure, choose a scenario, and watch the Command Center. The incident will appear in your dashboard, ECHO will post in your Slack war-room, and you will see the full agent lifecycle in real time. Each scenario can only be injected once per environment, while your trial is still active — resetting doesn’t restore the ability to re-inject it. If you want to run the same scenario again later, terminate the environment and provision a new one (this does not reset your trial’s clock or diagnosis count — see Demo vs Adopt). After the incident fires, sureops routes you to the Command Center so you can watch the response unfold in the real product rather than in an onboarding overlay.

​

Resuming the tour

If you closed the tour partway through, you can resume from where you left off: go to Settings → Onboarding and click Resume tour. Each step shows its current status (complete, skipped, active, or pending) so you can see at a glance what is left.