---
title: "The peaceful way to ship software, static outbound IPs and IPv6 in the CLI"
date: 2026-07-03
number: 0297
url: https://railway.com/changelog/2026-07-03-the-peaceful-way-to-ship-software
---

# The peaceful way to ship software, static outbound IPs and IPv6 in the CLI

Take a deep breath, drop your shoulders, and unclench your jaw. We launched a new campaign to help developers like you find your peace: [The peaceful way to ship software](https://railway.com/peace). The Railway CLI also picked up outbound networking controls, with new commands for static outbound IPs and outbound IPv6.

Let's get into it! 🚄

## The peaceful way to ship software

[Image: Find your peace at railway.com/peace]

Has a developer you know lost their peace? Is that developer you?

This week we launched a campaign to help developers like you find your peace. You can check it out at [railway.com/peace](http://railway.com/peace). We won't spoil it, but you may feel different afterward. And yes, that really is [Gilfoyle from Silicon Valley](https://www.hbo.com/silicon-valley), not AI.

Watch the film on [X](https://x.com/Railway/status/2071619522570637586), [LinkedIn](https://www.linkedin.com/posts/railwayapp_has-a-developer-you-know-lost-their-peace-activity-7477386611211587584-yHcp), or [YouTube](https://youtu.be/HtmvvzNphB8), and send it to a developer who needs it. The campaign is out in the physical world too. If you spot it around the Bay Area or New York, grab a picture and tag us.

## Static outbound IPs and IPv6 in the CLI

[Image: Manage static outbound IPs and outbound IPv6 with railway outbound-network]

Outbound networking joins the CLI with the new `railway outbound-network` command:

- `railway outbound-network status` summarizes static outbound IPs and outbound IPv6 for the selected service and environment.
- `railway outbound-network static-ip enable` and `disable` manage static outbound IPs. Status reports the assigned IPv4 addresses and whether the assignment is high availability, and changes take effect on the next deploy.
- `railway outbound-network ipv6 enable` and `disable` stage an environment config change, matching the dashboard toggle. Apply the staged change to roll it out.

Static outbound IPs matter when something outside Railway allowlists traffic by source address, like a payment provider, a partner's firewall, or a database in another cloud. The commands support the standard `--service`, `--environment`, and `--project` selectors along with `--json`, and JSON output includes a lifecycle object that tells automation whether an action applied directly or staged an environment change.

Before this, both features were dashboard toggles. The CLI now exposes the same controls in a scriptable form, so an engineer or agent can read the current state and flip them from the terminal.

Update with `railway update`, read the [static outbound IPs docs](https://docs.railway.com/networking/static-outbound-ips), run `railway outbound-network --help`, and let us know what you think on [Central Station](https://station.railway.com/new?type=feedback).

## Fixes and improvements

- We shipped hosted MCP support in the [Railway plugins](https://github.com/railwayapp/railway-skills) for Claude Code, Codex, Cursor, and Grok. The plugins now connect to Railway's hosted MCP server for one-click setup, where they previously configured a local MCP server through the CLI.
- We improved the `use-railway` agent skill by refreshing it against CLI v5.23.3, so agents route work through the CLI's config, CDN, WAF, and networking commands instead of older config-patch flows.