LoginSign Up
← Back to all sparks
R

Railway

INFRA · APIS
Velocity5.0

Cloud platform for deploying and hosting applications, databases, and services

railway.com ↗

Railway lets other tools hand work to its cloud agents via MCP, the CLI or the API.

paascloud agentsmcpclisecuritymanaged databases
◆Current state
Railway's November 13 release opens Cloud Agents to outside callers: tasks can be handed over through MCP, the CLI or the API, `railway ca` sorts threads by status, and Agent Connectors no longer require Priority Boarding. It follows two security-focused releases after the October 21 incident: automatic patching and credential-regeneration redeploys, then workspace token review, HA database password rotation and CLI tracing.
◆Where it's heading
After a month spent on post-incident security, Railway is back to building its agent layer, which started with OpenCode on Cloud Agents and ChatGPT and Claude subscriptions in September. The aim is for agents, not only people, to drive deploys on the platform.
◆Prediction
Expect Cloud Agents to get more ways in and more control over what they can touch, likely tied to the workspace token and permission work from early November.

◆Recent moves

  1. 15h ago

    Cloud Agent tasks, a better `railway ca`, Agent Connectors

    Cloud Agents can now take tasks from MCP, the CLI or the API, threads can be managed by status, and Agent Connectors leave Priority Boarding. The release note is short, but it marks Railway's return to agent features after a month of security work.

    View source ↗
  2. 8d ago

    Workspace token management, password rotation for HA databases, tracing in the CLI

    Workspace token review and revocation, dashboard password rotation for HA databases and railway trace in the CLI. Two of the three are credential controls, continuing Railway's post-incident tightening.

    View source ↗
  3. 14d ago

    Automatic security patches, redeploys after credential regeneration

    Railway now rolls security fixes out to affected service images and function runtimes, and redeploys connected services when database or bucket credentials are regenerated. Arriving a week after the incident update, it moves two chores from customers onto the platform and fits the steady shift toward production-grade operations.

    View source ↗
  4. 21d ago

    October 21 security incident

    A disclosure, not a release: Railway summarizes its October 21 security incident, links a preliminary report and lists recommended actions for customers. After two months of production-readiness features, how it handles this incident is the real test of that positioning.

    View source ↗
  5. 28d ago

    Activity feed filters, guided IaC migration, cron jobs in the CLI

    A guided move to infrastructure as code with explicit cutover and undo steps, cron runs from the CLI and filterable activity feeds. It continues the post-August pattern of operational controls around the agent stack, here aimed at teams moving from dashboard clicks to code.

    View source ↗
  6. 1mo ago

    Railway Authentication for domains, OpenRouter support, iOS rename

    Railway Authentication puts a login gate in front of deployed domains, adding another production control that teams would otherwise get from a separate proxy or auth service. OpenRouter support gives the agent stack one route to many models instead of another single-provider hookup, and the iOS rename is cosmetic.

    View source ↗