Hosting & Infrastructure

How our Railway-hosted products are deployed, isolated, and operated — and how that differs from the Bedrock AWS platform.

Our commercial SaaS products are deployed on Railway, a managed platform that handles the underlying compute, networking, and TLS termination. Each product is a container image built by the same CI pipeline described in CI Guardrails, scanned before release, and promoted to a pinned image tag that the platform runs.

Deployment model

• Container images, built and scanned in CI. Images are produced by the project pipeline, scanned for HIGH/CRITICAL vulnerabilities, and only then promoted to the tag the environment runs. The platform runs a pinned tag rather than auto-pulling latest, so a deploy is a deliberate act.
• Managed TLS. Transport is encrypted end to end; the platform terminates TLS at its edge and the application is reached over HTTPS.
• Managed Postgres. Persistent data lives in a managed PostgreSQL database provisioned per product, reachable only by that product's service.

Isolation

• Per-product services. Each product runs as its own service with its own database; products do not share application runtimes or data stores.
• In-application tenant isolation. Within a product, tenant separation is enforced in the application layer under the tenant-scoping invariant — every scoped query carries a server-derived tenant identifier that is never accepted from the client.
• Secrets in the platform, not the image. Configuration and secrets are injected as environment variables at runtime; they are not baked into the image and are not committed to source control.

How this differs from the Bedrock platform