Product Tiers & Capability Packs
A path from understanding to guided improvement
ODIN is organized around maturity and outcomes, not arbitrary feature gates.
The working MVP 1 product-tier model is:
| Edition | Goal | Narrative copy |
|---|---|---|
| Community | Understand | Safe environment map, evidence-backed readiness, observability, and advisory update guidance. |
| Plus | Organize and Track | Operational knowledge, history, tracking, and a recurring Technology Health rhythm. |
| Pro | Improve and Automate | Guided workflows, richer context, and automation-ready capabilities. |
| Managed | Operate and Optimize | Dravenkor expertise, reviews, support, and ongoing improvement. |
DORI remains part of the ODIN experience across editions. Higher editions add context, history, workflows, automation options, support depth, and capability breadth.
Capability-pack framing
Capability Packs are outcome-focused capability areas. They should help users understand what a feature area is for, not force the site into a feature checklist.
For the first Community proof loop, these pack concepts matter most:
| Capability area | Community proof-loop role |
|---|---|
| Network Map & Discovery | show environment shape and relationships |
| Assets Pack | curate service/endpoint records and ownership context |
| Watchtower / Observability | show monitoring, alerting, readiness, and telemetry status |
| Recovery | show backup and restore evidence |
| Patch & Update Advisory | identify update pressure without executing changes |
| Knowledge | connect runbooks, documentation, and operational context |
| DORI | explain evidence and recommend next action |
The point is not to name every future pack on the first site. The point is to show that Dravenkor has a coherent packaging model for growing from Community validation into paid and managed value.
Reviewer questions
- Does the product path feel staged?