Skip to content
Launch Rail
Design-partner pilot

Customer-owned infrastructure, generated for the Launch Rail blueprint.

Terraform Base is the infrastructure artifact layer for the supported AWS pilot path. It translates a versioned Launch Rail blueprint into a reviewable plan that runs from the customer environment and keeps cloud credentials under customer control.

Generated foundation

Infrastructure that matches the product contract.

The pilot focuses on a reproducible plan, explicit prerequisites, safe retries, and a clean handoff—not a claim that every cloud and topology is already interchangeable.

Reviewable infrastructure plan

Preview the resources and dependencies from the customer environment before an apply is authorized.

Versioned Terraform artifacts

Keep infrastructure inputs aligned with the selected blueprint and locked module versions.

Secret references only

Generated manifests reference customer-controlled secrets instead of writing credentials into project files or logs.

Service-ready foundations

Model the networking, runtime, data, and messaging prerequisites required by the supported blueprint.

Plan and deploy from the customer machine.

Launch Rail does not need to receive or store the credentials that control the customer cloud. The CLI reads ambient AWS credentials, generates artifacts, and performs the supported pilot workflow locally.

customer-terminal
$ lr doctor
✓ prerequisites checked
✓ credential source: ambient AWS profile

$ lr plan
✓ blueprint dependencies resolved
✓ infrastructure plan ready for review

$ lr deploy aws
→ apply runs from this customer environment

Pilot acceptance boundary

  • The plan resolves only supported blueprint dependencies and versions.
  • Generated files and logs contain secret references, not cloud credentials.
  • Your team approves infrastructure changes before apply.
  • Retry and recovery steps are documented for the supported AWS path.
  • GCP remains planned until it passes an equivalent deployment gate.

Deployment review

Bring your AWS constraints before the pilot begins.

We will map regions, network ownership, data services, secrets, DNS, observability, and approval boundaries to the documented pilot path.

Talk to engineering