--- title: "Bring Railway to Work, Instant GitHub Repo Loading, Quick SSH" date: 2025-07-18 number: 0247 url: https://railway.com/changelog/2025-07-18-whats-stopping-you-from-using-railway-at-work --- # Bring Railway to Work, Instant GitHub Repo Loading, Quick SSH Before we get started, we wanted to let you know that Railway Founder [Jake Cooper](https://x.com/justjake) is on a new podcast that you can check out called [The Peel](https://x.com/ThePeelPod/status/1946283947102556421). If you want a peek into the proverbial locomotive here at Railway, check it out on [X](https://x.com/ThePeelPod/status/1946283947102556421), [YouTube](https://www.youtube.com/watch?v=2fzbv-3gTBI), [Apple](https://podcasts.apple.com/us/podcast/solving-the-hardest-problems-in-dev-tools-jake-cooper/id1694440669?i=1000717944944), or [Spotify](https://open.spotify.com/episode/5RJlod18p58qVD6Ssduljt). And speaking of management, if you’d like to join ours, we’re looking to fill a [large number](https://railway.com/careers#open-positions) of senior engineering positions. So if your company management [recently attended a Coldplay concert](https://x.com/PopCrave/status/1945838356249669926) or [decided to shell itself to a tech giant](https://x.com/JustJake/status/1944186601502126568), we’d like to invite you to work with us instead. (And if you think you know a world-class head of engineering, [Ian](https://x.com/igk) would like to meet them.) In other exciting news, [Mahmoud](http://twitter.com/thisismahmoud_) just joined the Railway team as a DevRel Engineer! If you have issues or product feedback, PLEASE feel free to [drop him a line](https://x.com/thisismahmoud_). He's essentially our human suggestion box (and surprisingly, he's excited about it). Ok, that’s all we got. Let’s jump into it! ## Get Paid to Bring Railway to Work Check out [Railway’s affiliate program](https://railway.com/affiliate-program). You can earn a whopping 15% commission on every dollar your referrals spend on Railway within the first 12 months. Bring Railway to work, get paid big bucks. The Railway team is collecting requirements for large organizations and we’re earmarking time to see if there are any blockers to you getting your check. Is there a specific requirement your company has or a feature that Railway doesn't have yet that's holding you back? Whatever it is, we'd love to know about it. You can share your thoughts on this [Central Station post](https://station.railway.com/questions/what-s-stopping-you-from-choosing-railwa-9dda6d93) or just hit reply to this email. ## Instant GitHub Repo loading Creating new projects just got a whole lot faster. We've rolled out faster GitHub repo loading to everyone after having it behind a feature flag last week. If you’re experiencing any slowness, [let us know in Central Station](https://station.railway.com/). [Image: GitHub repos now load much, much faster] ## Quick SSH (Copy command) Got Railway services deployed but need to peek under the hood? The Railway CLI lets you start a shell session inside your running services. This is ideal for those times when you need to debug something live, run some commands, or inspect files without needing to redeploy. Just right-click your service in the dashboard and click “Copy SSH command” to copy the exact command you’ll need. Keep in mind this uses Railway's custom protocol (not traditional SSH), so there are some limitations around things like file transfer and SSH protocol features. Check out our [newly released documentation guide](https://docs.railway.com/guides/cli#ssh) to learn more about getting started and best practices. [Image: “Copy SSH command” button to SSH into your services using the Railway CLI] ## Fixes and Improvements - We made invoices more clear since the Railway Metal discount is now the default - We fixed an issue that sometimes resulted in a broken integration state with GitHub - We made the restore backups button, less scary. Boo! - We made the projects usage pages load faster - We fixed an issue where workspace members can see the project usage pane - We shipped a change where random 504s should stop returning in the API. We’re not sure if we eliminated this class of problem, but we found that Websocket sessions within the project canvas would build up state to the point where it block Node’s event loop and then would cause 504s on API responses. *So much for “non-blocking” I/O huh?* - We fixed an issue with DB performance on our fleet by alerting on some metrics within our storage cluster. We’re actively triaging this issue and further fixes are inline, p50s should be faster, p99s are next in line for a fix next week. We appreciate your patience.