Public roadmap · 1 → 100

The Ascension Ladder

One scale from first impression to civilization-grade infrastructure. Levels 1–7 are spelled out; 8–100 are shipped as bands so we can assign real releases inside each band without maintaining ninety duplicate bullet lists.

Interactive explorer

Drag the slider — see which band you are exploring and what to tighten next.

1

Levels 1–7 (detail)

1
Presence & story

Clear brand, hero, differentiation, CTAs, ecosystem hooks.

2
Prove the basics

Legal/trust, status, DPA/PCI plain language; guided first deploy with real screenshots.

3
Product depth

Panel preview, honest comparisons, docs written against your real panel.

4
Automation truth

Public API = shipped API; OpenAPI/Terraform starter; calculator without “contact sales” for common SKUs.

5
Scale proof

Named stories + metrics; SLA appendix tied to monitoring; reseller runbooks.

6
AI contracts

Data flows, retention, recording/law, provider boundaries, human handoff, limits.

7
Platform OS

Unified identity + billing graph; webhooks + audit export + RBAC; partner marketplace.

Bands 8–100

Each band is many micro-releases. Pick one user journey and climb it vertically before spreading wide.

8–15

Reliability engineering on display

  • SLOs / error budgets per surface
  • Game days + redacted postmortems
  • Chaos drills on deploy / resize / restore
16–25

Security as a product

  • Bug bounty + disclosure SLAs
  • SSO/SAML + SCIM story
  • Data residency + key custody options
26–35

Compliance & procurement

  • SOC2 / ISO where real
  • Subprocessor register + DPIA templates
  • Enterprise MSA + order schedules
36–45

Network & edge

  • Measured p95 by city
  • Private networking limits + pricing
  • LB + health checks + canaries
46–55

Data platform maturity

  • Legal hold + WORM tiers
  • Cross-region failover stories
  • SIEM export of metrics/logs/traces
56–65

Developer experience at scale

  • SDKs from OpenAPI
  • Prod-like sandboxes + ephemeral envs
  • Deprecation windows
66–75

FinOps & fairness

  • Transparent egress math
  • Commitment + spend dashboards
  • Team chargeback + anomaly alerts
76–85

Ecosystem gravity

  • Certified partners + rev share
  • Regulated reference architectures
  • RFC + public roadmap voting
86–92

Global operations

  • Follow-the-sun + severity matrix
  • Language coverage where promised
  • Incident playbooks (summary public)
93–97

Research-grade

  • Reproducible benchmarks
  • Co-design narrative where true
  • PQC roadmap only if serious
98–100

North star

  • 98 — Standards leadership tied to shipped code
  • 99 — Multi-continent active/active proofs
  • 100 — Critical-infrastructure posture (only if literal)

How we ship against 1–100

Vertical slices

Choose a journey (DNS change, backup restore, first VPS). Move it from level 2 (provable) through 4 (API truth) before painting new surfaces.

Never skip truth

Levels 2–3 beat louder adjectives. Anything customer-touching gets status, docs, and screenshots before we claim it at scale.