7 comments

[ 4.6 ms ] story [ 26.2 ms ] thread
How's the per seat pricing working out for you? I'd see a lot of people just using a shared login for this.
There’s definitely some of that. In my experience, pretty much every “Teams” product is really just for larger orgs to simplify orchestration. Plus people pay for usage regardless.

We’ll be adding more team centric stuff (more granular permissions, SSO, etc) to make this a bit more appealing/collaborative

Vercel solves this by basing it on the github user that's pushing to the repo. Something to consider.
That's a neat idea. I wonder if that breaks down for open-source repos with lots of contributors, or does Vercel have different pricing in that case?
I’m not using Railway in production, but I have been using it as a test DB to learn some new tools. It was recommended in a Discord group after people were having issues with how Heroku rotates keys for the hobby tier. The UI was way more intuitive. Didn’t even have to reference the docs to get going.
I'm kinda surprised someone hasn't made a script to grab the new connection string and update the value in a secrets store when it stops working / Heroku rotates it.
My guess is someone that serious is ready to be off the hobby tier.