Product-domain modules
Identity, authorization, entitlements, notifications, media, submissions, and audit workflows share a consistent tenant model instead of behaving like unrelated projects.
One technical system
The backend capabilities your product needs—designed to work together.
Launch Rail combines source-owned domain services, shared engineering conventions, and a customer-cloud operating model. Your team starts from a coherent platform and keeps control of the code and deployment.
- Published as available
- 7 modules
- Available or open for pilot evaluation
- 12 modules
Platform capabilities
Power without hiding the boundaries.
Each lifecycle, dependency, interface, and deployment target is published in the product registry, so technical teams can distinguish what ships now from what is in pilot or planned.
Typed service contracts
Available services publish REST and Connect/gRPC interfaces from versioned contracts, with documentation and API references linked from the service registry.
Explicit data ownership
Transactional boundaries, PostgreSQL persistence, event delivery, retention, and provider choices stay visible in the architecture your team owns.
Operational conventions
Structured logs, OpenTelemetry conventions, health checks, migrations, and service configuration follow shared patterns across the ecosystem.
Customer-cloud deployment
The AWS path is being polished with customer-run deployment artifacts. GCP remains visible as a planned target until it reaches the same release gate.
Governed agent access
The Agent Gateway pilots selected MCP tools behind tenant scope, allowlists, authorization checks, budgets, approval rules, expiry, and audit events.
Interface model
Applications connect directly. Agents go through policy.
REST and Connect/gRPC remain the primary application interfaces for supported services. MCP access is presented through the Agent Gateway pilot, where tool exposure and mutations can be governed instead of making each service a public agent endpoint.
REST for broad application compatibility
Connect/gRPC for typed service calls
CloudEvents and NATS patterns for workflows
MCP through tenant-scoped Agent Gateway policy