DDoS Protection Now Default

Railway has partnered with Fastly to deliver automatic DDoS protection for every public service on the platform. All traffic now routes through Fastly's global network with 100+ points of presence, where malicious traffic is filtered before reaching your infrastructure. There's nothing to configure—protection is enabled by default for any service with a public domain.

Previously, customers had to bring their own DDoS protection by switching between Railway and external providers. This new default approach eliminates context-switching and removes the need to manage separate infrastructure. Railway is also building CDN caching on top of this partnership for future releases.

Domain Registration and Management

Railway has launched domain registration to Priority Boarding, enabling developers to search, purchase, and manage domains directly within the platform. Developers can now:

• Search across 250+ TLDs from Railway's networking settings or at railway.com/domains
• Get AI-powered domain suggestions based on project descriptions
• Automatically configure DNS when purchasing a domain (no manual record copying)
• Enable WHOIS privacy and auto-renewal by default on all domains
• Manage renewals, expiry dates, and payment status centrally at railway.com/workspace/domains

Pricing is set at cost, rounded to the nearest dollar. This eliminates the traditional workflow of purchasing domains elsewhere, copying DNS records, waiting for propagation, and verifying configuration.

Canvas State Per Environment

Canvas layout state is now scoped per environment instead of shared across all environments. This addresses issues where:

• Multiple environments with different service counts would show phantom nodes
• Concurrent editing by team members could result in layout conflicts
• Template deployments would position services incorrectly in target environments

Now developers can customize canvas layouts independently for production, staging, and other environments. Layouts copy when creating new environments but remain independent thereafter, allowing teams to organize by dependency chain in one environment and by team ownership in another. Developers can import layouts from other environments via canvas settings.

Additional Improvements

• Template deployments now include variable autocompletion, markdown support in descriptions, and better handling of optional variables
• Canvas centers services when the right panel is open
• Fixed missing GitHub installation error visibility
• Corrected domain configuration modal to prevent malformed DNS records
• Command palette now accepts GitHub URLs in the GitHub Repos sublist