Viewing profile — justjake

Appreciate the feedback. We got some feedback previously that things were "too technical" and not acknowledging it from the what users saw. I've gone ahead and re-added the surroga…

We indeed run tests as well as stage releases. For this issue, when rubber met road in production, we saw cases which weren't visible in staging. We've rolled out some changes (det…

> Honestly for a production-grade _platform_ company, that also does compliance (SOC2/3, HIPAA etc.), not having a staged release is negligent, and how you guys are handling this i…

Railway founder here, providing some color > Why were they making CDN changes in prod? With their 100M funding recently they could afford a separate env to test CDN changes. Did th…

Would you mind pointing out these claims? Happy to address them personally

Fixed the typo in that second paragraph and aligned the section on the Set-Cookie stuff. Anything else that can be made more clear?

Totally! People who see the impact will likely see more impacted than say, 3% of their services. Not all disruption created equal. We rolled out a change to update our fraud model,…

Railway founder here. That said, we treat this exigently seriously! Any downtime is unacceptable and we'll have a post mortem up in the next couple hours

Hello! Railway founder here We'll have a post mortem for this one as we always write post mortems for anything that affects users Our initial investigation reveals this affects Apo…

Jake from Railway here > And my hosting provider is saying, "you are not allowed to push out your urgent fix, because we see that your app contains a far less urgent problem." Ther…

Bingo. Nix doesn't give you a generalizable-across-languages-and-ecosystems way of specifying specific versions without blowing up your package size, unless you hand Nix to your us…

Hey y'all! 3 years ago we built Nixpacks. However, we ran into some pretty large pains using Nix for dependency resolution So today we're rolling out Railpack, the successor. It re…

We're actually profitable on this round of funding. We've venture backed, but we also wanna make sure people know we're here for the long haul.

Author here. We've talked previously about our datacenter buildout ( https://blog.railway.com/p/data-center-build-part-one ) This is the "next step". We're using our baremetal pres…

We use ~~arch~~ nix BTW I think, least for us, this is tablestakes stuff. You should be able to get the repo going day 1 and get a commit in But there's just a fuckload of context …

Happy to answer any questions. This all seems very obvious in retrospect, but I wanted to share for any other early stage companies in the hopes people can avoid some scaling pains…

That $0.10 per GB is direct pass along for the cloud ingress fees We can lower that once we’re fully on metal

FWIW this is the advantage of being able to run in the cloud and on perm If we have to we can “burst” into the cloud

We're blessed with some kickass investors. They gave us just the right level of scrutiny. We were super clear about why we wanted to do this, we did it, and then they invested more…

Not ATM. We use it in a lot of our stack, so we will likely pull it in in the future

Thank you! Anything you think we can do better?

FWIW, we just pass the costs on from the current cloud providers. Doing this work will let us lower those egress prices!