We actually only charge you for what you use. As a result people often see 30%+ savings when moving stuff over from other providers (especially Heroku)
255 karma · joined November 20, 2019
We ack'd this and then pretty heavily to making it stellar, so if you're still having issues please let us know (that should not be the case)
Best, Jake from Railway
https://railway.com/changelog/2024-09-20-railway-metal-beta#...
But yes, convention over configuration (and we still expose the knobs if you want em)
Ian is our recruiter, I checked AshBy, and basically everyone's getting at least a "Sorry you're not a fit" email (save for people spamming the inbox multiple times)
As for why we've posted the same job many times. We're an early stage infrastructure company, and it's surprisingly hard to find people who go really deep (Example: We've built our own orchestrator, so we're looking for people who would build kubernetes instead of use it)
Tired of trying to beat kube into shape? Does writing YAML to ship code fill you with utter dread? Dream of a future where deploying software is simple, and you don't need an army of infrastructure engineers to build that perfect janky bash script™ to make life easy?
We're Railway, and we think infrastructure can be better. So far we've built out a platform loved by hundreds of thousands of users who simply tell us "Give me Postgres", "Deploy this repo", and we make it happen
We were recently named to the 2023 Nasdaq "Enterprise 30" list: https://www.enterprisetech30.com/list
Fair warning! The problems are complex: home-rolled hypervisors, cut-above container orchestration, over/under/whateverlay networks, virtio device drivers, edge proxies, IAM that doesn't suck, kitchen sinks - we need to build it and we're looking for likeminded individuals who think this stuff is fun.
If that sounds like you, please apply at railway.app/careers. We have a number of roles, but are prioritizing the following:
Platform Engineer - General
Platform Engineer - Orchestration
Support Engineer
Solutions Architect
See you soon, and happy shipping.
Tired of trying to beat kube into shape? Does writing YAML to ship code fill you with utter dread? Dream of a future where deploying software is simple, and you don't need an army of infrastructure engineers to build that perfect janky bash script™ to make life easy?
We're Railway, and we think infrastructure can be better. So far we've built out a platform loved by hundreds of thousands of users who simply tell us "Give me Postgres", "Deploy this repo", and we make it happen
Fair warning! The problems are complex: home-rolled hypervisors, cut-above container orchestration, over/under/whateverlay networks, virtio device drivers, edge proxies, IAM that doesn't suck, kitchen sinks - we need to build it and we're looking for likeminded individuals who think this stuff is fun.
We're currently prioritizing hiring for three critical roles:
If that sounds like you, please apply at railway.app/careers. We have a number of roles, but are prioritizing the following:
Platform Engineer - General
Platform Engineer - Orchestration
Support Engineer
See you soon, and happy shipping.
So there is one but, if you can't find it, it's as good as there not being one!
It's currently located at https://nixpacks.com/docs/guides/configuring-builds#change-w...
Is there some place you'd expect it to be instead? All ears on feedback!
Could you bump the email in my inbox? Even if you hate my guts and have no interest in the company, I‘d like to know cause I don’t recall this at all :(
We do a 30 minute screen with me (to protect our engineers time) and share the problem ahead of time (to not surprise the interviewee)
Can you mention what particularly was unstable?
Would love to drop image sizes
We could jam back and forth on this but generally we're not dogmatic about the "middle" of the process, and we suspect the implementation will change over time for a variety of reasons (even faster builds, smaller images, less dependencies, etc).
The only thing we're dogmatic about is the experience and the fact that it emits an OCI compliant image (that can indeed be run on any orchestrator).
If you're interested in contributing or jamming on this wanna shoot me a DM on twitter (JustJake) or email at jake at railway dot app?
See: https://github.com/railwayapp/nixpacks/blob/f88718efe1156671...
Our goal is to make reproducibility more approachable/less cumbersome, and for people to be able to define additional nix/apt/etc packages added to the container .
You can add package you'd like via the environment variables NIXPACKS_PKGS (or NIXPACKS_APT_PKGS for apt)
Nixpacks can also spit out a plan (https://nixpacks.com/docs/how-it-works#plan) which, when run again, will assure that the build artifacts the exact same every time it's run against that plan.
The result is that any code that's built with nixpacks has all it's dependencies snapshotted so it won't break over time.
For us, that means anytime someone comes to our platform (http://railway.app/) and deploys an Template, it won't be broken
BuildKit makes this possible and we've got lots of stuff planned. Would love to hear anything you can think of that would make this more friendly!
We're the people behind nixpacks; happy to answer any questions just holler
OP might wanna consider putting in a credit card before trying to do HN scale next time
We had some pretty massive issues with an email provider. Have since switched to Postmark. Apologies there and totally understand that absolutely blows.
I can tell you a couple things off the bat:
- We have automated backups but they're for our own internal disaster recovery. User backups are something we want to do but haven't put on our roadmap yet
- A key thing with Railway is "It's just code". So, a worker is just another service. We don't have special casing for specific types of code. We just run the code! So, yes we do support them
- We have a lot of stuff built in, but we also support deploying say, a containerized DataDog agent, or a Dockerized sidecar, or application level Sentry integrations
We have a very particular vision of how this stuff should be done, so it's going to take some time. My promise is to always be super honest about the platform, so it would be more of an "Customer Discovery" vs a Sales call
If that all sounds well and good, you can email me at jake@railway.app! Offer goes for anybody interested but again, I'm not here to push the platform just to gain clarity on what we're building :)
They build cool shit, they blog about their cool shit, because it's cool shit.
Background: Founder of Railway.app here.
There's a lot of these companies popping up that offer a "Heroku replacement", and once you dive in, you realize you have to pay $300/mo for a Kubecluster + $200/mo for the wrapped Kube service
In our experience, people move off Heroku for a couple things:
- Cost: Kinda self explanatory but Heroku pricing ramps hard
- Flexibility: Heroku's not great for anything beyond stateful monoliths
- Scalability: Notoriously Heroku's SLAs aren't that great
In my mind, you don't replace Heroku with a minimum $500/mo Kubernetes cluster. Not only is this cost prohibitively expensive, but Kubernetes itself is a jet engine, and if you're not trained to use it correctly, you can risk catastrophic failure (on costs ballooning, on dataloss, etc)
We're working hard at Railway to provide not just a Heroku replacement, but a next generation, composable infrastructure canvas. $5/mo, 30 seconds, and you're up and running.
Demo:https://user-images.githubusercontent.com/5499880/165187948-...
Would love any feedback and thoughts people have about Heroku, my thoughts above, and what we're building :)
EDIT: Wow, just went from 11 -> 8 upvotes. I suppose they didn't like the astroturfing callout
EDIT2: Render isn't who I'm talking about. They're great.
You can give us a go at https://dev.new/
We're working on making the project connections a bit better so that generalizable connected services are as trivial to build as stateful monolithic backends in the current platform
Anything else we've missed and I'm happy to sit down with you (or anybody else) and hear what your needs are. Arbitrary evented triggers are coming pretty soon as well as the API so the infrastructure should be fully composable/meta.
P.S We integrate with the lovely lads/lasses/fiends at Vercel :)
We’ll be adding more team centric stuff (more granular permissions, SSO, etc) to make this a bit more appealing/collaborative
Railway is collaborative software infrastructure with superpowers. It's as simple as CMD + K -> Postgres to provision whatever containers you need. We also offer cloud environments for all team members, a CLI to route all the container-relevant environment variables to your programs, and plugins like (e.g Postgres) which interface with your favorite libraries (Prisma, Knex, etc).
Our goal is to offer the fastest experience from zero to production application. We're at about 15 minutes for developers, and we want to get that down to 5 minutes, for anybody.
Our Core Tech:
Frontend: TypeScript, React, GraphQL.
Backend: TypeScript, Node, Golang, Prisma.
Databases: Postgres.
Infrastructure: Ansible, Terraform, Docker, CloudFlare Workers.
About Us: Really small team (3 ATM), all engineers. Backed by some of the biggest names in devtools. Well capitalized and lots of equity in the table if you want to tune the slider either way (Cash or Equity)
If you're interested, play with the product and shoot me an email jake at railway dot app (Please cc jobs at railway dot app so that it lands in our Discord). Looking forward to hearing from you!
Product: https://railway.app/invite/y2-r-nkin3F69OMlwpcvR
Infra Eng: https://www.notion.so/railwayapp/Infrastructure-Engineer-3ba...
Full Stack: https://www.notion.so/railwayapp/Full-Stack-Engineer-0c78646...