Railway

Railway

@railway.com

The all-in-one intelligent cloud provider Railway.com

435 followers5 following118 posts

Railway has been named part of the #Disruptors60 by @TechCrunch 🎉 Our mission has always been to get compute in the hands of every builder. With agents, everyone is a builder. Build with us.

We're adding support for OpenRouter to Priority Boarding users in Railway Using OpenRouter lets you access wider models for all things agents, whether its our harness in Cloud Agents, or our bots. Models like Grok 4.7, Muse Spark 1.3 and more What models do you want next?

You can now use your @ChatGPT subscription in Railway Once connected, you can set your default model to GPT-6 Astra, GPT-6.1 Sol or GPT-6 Luna, and use them with the Railway Agent, Discord / Slack bots, or in "railway code" Enable it in Priority Boarding Happy building!

It's a bad day to be a slow (or broken) request 🔍 Tracing is now in preview. You or your agent can follow any request end to end, pinpoint what's slow or failing, and fix it Opt in, then set it up from the Traces tab railway.com/account/feature-flags

We're excited to be part of the launch announcement of the Muse Connector Platform Manage your deploys, ship code, and more on Muse with Railway

Congratulations to @SpaceXAI on the @grok 4.7 drop, we've all been waiting! It's very fast, and the intelligence is quite good. Running multiple cloud agents with it now Spin it up in cloud agents with `railway code --grok`

Announcing: Railway Sandboxes Spin up thousands of VMs right next to your infra on Railway Run, checkpoint, and fork and let your agents (and code) run

🆕 Forward email from your Railway domain to your existing inbox • Custom addresses like hello@yourdomain.com • Automatic DNS setup • Built-in test emails Available for domains purchased on Railway with Railway-managed DNS

🆕 Guardrails for Enterprise workspaces Set a policy once and enforce it across every project, in the dashboard and the API. Here's what you can lock down ↓

View full thread

You can restrict deployments to approved sources: only GitHub orgs you allowlist can ship, and it's a hard boundary, even for admins Personal repos, CLI deploys, Docker images, and templates are all blocked, official database templates can still be deployed

🆕 Guardrails for Enterprise workspaces Set a policy once and enforce it across every project, in the dashboard and the API. Here's what you can lock down ↓

Restrict generate domain stops non-admins from generating public *.railway.app domains, so internal services stay internal • Non-admins see a banner explaining the restriction • API requests are rejected • Auto-generation is skipped for templates and new environments

Restrict TCP proxy does the same for raw TCP: non-admins can't create public TCP proxies, so there's no accidentally exposing your database to the internet Neither policy touches custom domains or private networking between services, and admins keep full access