Stratosphere

Interrogate. Explain. Accelerate.

Stratosphere is a Kubernetes-first migration architect for legacy enterprise applications. It observes how a VM actually behaves, explains what it found in plain language, and produces a governed migration package engineers can review and deploy safely — without guessing.

---

What it solves

Enterprise VMs accumulate years of undocumented runtime behavior. Modernizing them by hand means weeks of interviews, stale wikis, and high-risk guesswork. Stratosphere replaces that by capturing live runtime evidence, decomposing it into deployable workloads, and producing a complete Kubernetes migration package with review and approval gates before anything changes.

---

How it fits with existing tools

Cloud and vendor toolchains can already generate containers or migration assets for many stacks. Stratosphere is the layer that makes modernization usable and governable for teams who do not live in infrastructure every day:

• Decision and communication first: plain-language intake, current-state map, future-state options, and “what to validate next”.
• Evidence-based recommendations: confidence + unknowns + rationale for why something is a Deployment, StatefulSet, or CronJob.
• Governance built-in: review, approvals, preflight checks, and a blue/green cutover plan that change boards can audit.
• Agent-accessible: MCP tools let an enterprise Copilot/agent drive the workflow while keeping outputs deterministic and reviewable.

Stratosphere is not “click-to-migrate” in v1. It produces artifacts and an execution plan that humans (typically platform teams) deploy after sign-off.

---

What you get

Artifact	Description
Dockerfile per workload	Minimal, layered, ready-to-build
helm/ chart	Values, templates, secrets scaffold
terraform/ scaffold	Namespace, RBAC, storage provisioning
reports/migration-summary.md	Plain-language overview for stakeholders
reports/executive-summary.md	Decision-ready brief for app owners
reports/readiness.{json,md}	Readiness score, blockers, confidence
reports/business-impact.{json,md}	Customer, security, and effort translation
reports/cutover-plan.{json,md}	Blue/green stages and rollback triggers
reports/secrets-management.md	Detected secrets and injection guide
reports/roi-estimate.{json,md}	Cost and sustainment ROI model
reports/application-map-*.md	Current and future architecture maps

---

Single-binary install (on a VM)

For SSH-first environments, use the Linux executable from GitHub Releases.

VERSION=v0.1.0
ARCH=linux-x64 # or linux-arm64

curl -fsSLO "https://github.com/fairley46/stratosphere/releases/download/${VERSION}/stratosphere-${ARCH}"
curl -fsSLO "https://github.com/fairley46/stratosphere/releases/download/${VERSION}/SHA256SUMS"
grep "stratosphere-${ARCH}" SHA256SUMS | sha256sum -c -

chmod +x "stratosphere-${ARCH}"
mv "stratosphere-${ARCH}" stratosphere

./stratosphere doctor
./stratosphere mcp

Full on-box flow: docs/stratosphere/engineering/ON_BOX_QUICKSTART.md.

If you are running from this source workspace instead of a release binary, use:

npm run stratosphere -- --help

---

How to run it

From a runtime snapshot file:

stratosphere \
  --runtime-file fixtures/stratosphere/sample-runtime.json \
  --out-dir artifacts/my-migration

From SSH (live VM discovery):

stratosphere \
  --ssh-host 10.0.1.42 --ssh-user deploy \
  --intake-file my-intake.json \
  --out-dir artifacts/my-migration

Guided wizard (no JSON prep needed):

stratosphere \
  --wizard \
  --runtime-file fixtures/stratosphere/sample-runtime.json \
  --out-dir artifacts/my-migration

---

Ways to use it

Stratosphere has one engine with two main interactive entrypoints:

1. MCP (recommended for non-infra users) — Start stratosphere mcp and drive the workflow from your enterprise agent host (Opencode, Claude Desktop, etc.). The agent asks the questions; Stratosphere generates the bundle.
2. Interactive terminal wizard (lightweight TUI) — Run stratosphere --wizard ... to answer plain-language questions directly in the terminal. This is a prompt-driven terminal UI, not a full-screen TUI.

CLI (non-interactive) — Run stratosphere --help for all flags. Accepts snapshot files, local discovery, or live SSH. Optional: --strategy, --intake-file, --workspace-file, --export-provider. See docs/stratosphere/engineering/QUICKSTART.md.

For workspace development, npm run mcp:start and npm run stratosphere -- ... still work.

---

Documentation

Engineers

• Quickstart — install, run, extend
• On-Box Quickstart — SSH-first install and MCP flow
• Engineer Onboarding — architecture, CLI, MCP, tests
• Technical Architecture — package layout, engine internals

Stakeholders

• Product Overview — what it is, who it serves, what it outputs
• Pilot Execution Plan — how to validate with real workloads
• Backlog — roadmap and status

Enterprise / Governance

• Execution Workflow Spec — review → approval → preflight → execute
• Enterprise Readiness — rollout expectations
• Security Review — hardening summary and residual risks

Demo

• Demo Runbook — 12-15 minute walkthrough

---

Interrogate. Explain. Accelerate.