Describing OpsPilot
This page is the reference for how we describe OpsPilot in the docs - the positioning, the category, and the language rules. Apply it whenever you write about the product.
The key shift
System health remains the outcome. Continuous operational understanding is what sets OpsPilot apart.
Core messaging
| Element | Wording |
|---|---|
| Slogan | From telemetry to continuous operational understanding. |
| Core promise | Understand what matters. Act with confidence. Verify the outcome. |
| Main insight | Your team should not have to spend its day interpreting telemetry just to understand what matters. |
| Positioning line | OpsPilot is an AI observability platform that continuously interprets telemetry, connects evidence, and shows teams what needs attention, why it matters, and what to do next. |
| Category | AI observability platform with continuous AI-assisted investigation built in. |
| The shift we sell | From telemetry, dashboards, and alerts to continuous operational understanding. |
| Outcome | Less manual investigation. Healthier systems. |
| Customer benefit | Spend less time investigating monitoring data and more time resolving problems. |
The four questions OpsPilot answers
Frame features around the question they help answer:
- What needs attention?
- Why does it matter?
- What should we do next?
- Is the situation improving?
Brand architecture
- OpsPilot is the platform and the primary brand.
- Coworker is the AI capability built into OpsPilot that enables continuous investigation and rechecking.
Always build recognition for OpsPilot. Coworker is a capability of the platform, not a separate product, so lead with OpsPilot and describe Coworker as part of it.
Language rules
| Rule | Guidance |
|---|---|
| Retired | "Observability that keeps your systems healthy" as the lead line - "system health" is too generic to own. |
| Retired | "From dashboards to answers" - use the telemetry-to-understanding shift instead. |
| Retired | "Faster and easier than ever before" - too generic. |
| Changed | "What is the right fix?" becomes "What should we do next?" - this avoids overclaiming. |
| De-emphasised | "AI SRE" - crowded category language that can overstate Coworker. |
| Retired | "Assistant" - always use "Coworker". |