Railway: The Agent-Native Cloud — Jake Cooper

What It Covers

Railway founder Jake Cooper explains how his platform-as-a-service company scaled to 3 million users with 35 employees by building bare-metal data centers with 70% margins, developing agent-native infrastructure primitives, and treating the software deployment lifecycle as a loop to compress from days to seconds for both human and AI developers.

Key Questions Answered

• •Bare-metal economics: Building proprietary data centers yields a three-month payback period versus renting equivalent cloud compute, with hardware depreciating over four years. Railway maintains 70% margins on metal capacity, which subsidizes cloud-burst costs during demand spikes. Securing hardware debt against physical servers at prime-rate-plus terms provides cheaper capital than equity financing for infrastructure-heavy startups.
• •Agent-native CLI design: Exposing 40 arguments and 600 flags in a CLI is prohibitive for humans but ideal for agents, which treat dense option sets as high-value handles. Railway tracks where agents deviate from the happy path using telemetry, then adds routing arcs to reduce drop-off rates. Reducing a 12% deviation rate to 2% meaningfully accelerates agent loop-closure speed.
• •Staged VC selection: Each funding round should purchase a specific unfair advantage rather than maximum capital. Railway paired seed funding with operator mentorship, Series A with product-focused investors who provided autonomy, and later rounds with enterprise-sales specialists at Redpoint and FPV. Matching investor expertise to the company's current bottleneck compounds value beyond the dollar amount raised.
• •Production forking as safety primitive: AI SRE agents should never operate directly on production without copy-on-write environment cloning. Railway's model provisions a read-only production replica, applies PII transforms automatically, runs agent changes against near-identical state, then merges only validated diffs. Without these primitives, autonomous infrastructure agents will eventually corrupt production databases—a matter of when, not if.
• •Canvas as output, not input: Railway's visual infrastructure canvas is shifting from a human input mechanism to an agent output display. Agents use the CLI to make infrastructure changes while the canvas surfaces approval requests and context hierarchy for human oversight. Structuring the canvas as nested, infinitely drillable layers prevents organizational context from living only in individual engineers' heads.
• •Software development lifecycle compression: The pull-request model is being replaced by prompt-based iteration where agents author code and humans review rather than write. Railway internally mandates agent-assisted coding, targeting token spend where output reaches production. Feature flagging, shadow traffic, and progressive rollouts—previously only viable at Uber or Meta scale—become necessary for every team operating at agent-generated code velocity.