Render Raises $50M Series B
render.com
render.com
Funny enough I had big VC call me for due diligence (because I posted a lot on their forums and they spotted my name) and I happily told them how pissed I was with that change and how I went from vocal evangelist for the platform to looking for an alternative.
Still not as _terrible_ as Vercel which straight up doesn't deploy if the user isn't a paid org member lol. Now that is shameful as shit!
But this pricing change from Render was bad yeah. :(
We're looking for great people to join our team! See render.com/careers for all open roles.
Good luck
Second, have you guys had a chance to revise your hiring pipeline? When I spoke to your recruitment team a bit over a year ago they were asking for 8 straight hours on a zoom call as part of the software engineering interview. I had to drop out of the process because fitting that in was exceptionally difficult. (They did offer to split it into 5 and 3 but I still couldn't fit that in). They remarked they were looking to update that process a bit.
The above aside - I remember thinking everyone I spoke to there was pleasant and enjoyed working there. I was sad to have to drop out.
Best of luck moving forward.
I know this is my entitled Big Tech worker bias, but... surely there should be a lunch break?
8 hours is insane, do you compensate people for this time?
I was very impressed by render when I was investigating hosting platforms, but if I'm being honest I got scared away by the postgres pricing(free for only 90 days: https://render.com/docs/free#free-postgresql-databases).
Question: After some more research, I noticed that even among competitors there aren't really any "always free" options(e.g. even AWS directly only offers 1 year free for RDS). What is it that makes free-tier postgres so uncompetitive in comparison to hosted compute? Is it because dedicated disk is more expensive than shared cores?
https://supabase.com/pricing (not affiliated, but a happy user)
I'd like to give it a shot but I often don't get past HR because I'm in (theoretical) CS and lack "real world experience". Which is lame because the stuff I've done from my trench is amazing (source: trust me, lol).
Anyway, I'm really good on the backend, creating high performance REST APIs, documenting them, etc... and know a great deal of postgres.
I also have a good intuition for what's going to stick or not in the field. I was doing AWS ~15 years ago, back when you had to use an ugly SOAP interface to get things done, but I saw the potential and created the first automated cluster of bioinformatic tools in there. Right now, I'm betting on Rust, WASM, V8 isolates, and everything that has to do w/ lightweight function execution.
If that sounds good for render's mission, I'll be glad to take part in it.
> 100% employer-paid medical coverage and 99% employer-paid dental and vision coverage for you and all your dependents. FSAs available too.
1. Company starts to do X, makes it a wonderful experience
2. Users love it, it's successful
3. Company stop treating users well
4. New company steps into make X a wonderful experience again, with the advantage that the market is pre-validated.
How much of an advantage is it to know that users want what you're creating? Do you have any tips, like ways to reassure people you won't follow the same dynamic as the original company?
I wonder what the ideal time is in a company's arc to start their eventual replacement. Render just raised a series B which probably means they're still many years away from step 3, so it's probably too early. But maybe when they're raising a series C or D, it's time to start thinking about making their replacement.
I feel like Stripe is entering that territory right now. Not that they're worse than alternatives, but they no longer have that "wonderful experience" magic because they've started to turn on the maximize shareholder value engine.
With Render, I'd rather show than tell. As an interesting data point, we've now existed as an independent entity longer than Heroku did, and we're truly just getting started.
I was more asking about the tactics of the situation since it seems really different than the modal "would anyone even want this?" startup. It does seem like "show don't tell" is a good move.
I have _many_ tiny-usage projects, I'll say "10" but really many more. The thing is, even if you put their usage (resources, network, disk, etc) together it's still a "small" project equivalent, something that could run (capacity-wise) on a single VPS easily for $20-30/month. But the way Render is structured, even if I get 10 requests/month on each of them, I need to pay that per project. Which adds up quickly when you have many small projects as a hobby.
So I'm wondering if something like what Heroku had where there's a shared pool of 2000 credits that I can use among my projects as they get used by people, and when one of them becomes more popular then I can "upgrade" it to have a proper full-instance for each of its parts while keeping the rest of them in the pool.
If I wasn't so bad at devops, here the equivalent is I'd rent a mid-size VPS and have one folder/project, and I would be able to have them all hosted in that server with a lot of capacity to spare for $20-30/total. The way I have it now, if I wanted to host the same thing with Render, it'd be $250+/month only for my active projects. Heck, I think even my Raspberry Pi would be able to run all of these projects of mine properly (again, capacity-wise, I def love Render for its easiness of use).
I'm hosting a few using portainer and cloudflared on Synology NAS. This way everything is free, I have unlimited HDD and 10GB RAM. I keep running into some small issues and the CPU is terrible, but it works. :) Most of the time... Which is enough for me.
https://github.com/tomwojcik/homeserver-traefik-portainer
You just need to create a stack (in portainer) that has access to the git repo and select the compose file. That's more or less it.
I ultimately went with a large-ish droplet from DO with dokku installed. It’s been great, for the many small sites use case. It doesn’t scale, but that’s fine. When projects get traction the intention is to move them.
Which one has, and is now on AWS. But if we’d been on render I wouldn’t have moved it. I’d just spin up its own db and scale up the processes.
To do a bigger migration such as that I'd need a few days of solid personal work to learn how to do everything, I'll try to do it over the summer holidays, thanks!
A PaaS (depending on scope) can easily be the most complicated thing to build in the cloud, so the more building blocks you have, the better.
That's why I always look for profitable companies that have built a business around solid foundations rather than raising external capital in round B, C, D all the way to Z.
If you want to see how those companies *really* were doing, look at their stock prices after they go public. Very few go up or even stay flat. Most of them crash right after the stock handcuffs come off and the investors have passed the bucket to the general public. I even have an anti-portfolio of public companies with investors who wouldn't shut up for a minute about how amazing they are doing, when they were private companies. All of them have done considerably worse than the market average or any basket of tech companies, even excluding the big five.
There is a lot they are getting right
If a company is using Vercel to start up, they're pretty good for what you get, but eventually AWS (which Vercel wraps) will win out in pricing, even counting hiring devops/cloud/backend engineers.
rauchg disclosed their revenue trends recently https://twitter.com/swyx/status/1667995063216148480 i learned later that this interview was done in nov 2022
Some things I like about Render vs Heroku since switching:
- Building the container from the Dockerfile in my repo seems to be a lot faster because it keeps all of the image layers cached.
- I can control the external IPs that have access to my postgres database. I usually keep them all off and only let the webapp access it internally, and then whitelist an IP as needed.
- Env groups are nice - if I want to start another service I can have it use all the same environment variables vs trying to keep them in sync myself.
A couple of years ago they had some multi-hour outages but things have been pretty stable since, a couple of the multi-minute outages were on me as I was upgrading the database or messing around with some configs. https://status.pinnacleclimb.com/One thing I'd love in the future is some sort of postgres upgrade button. They handle minor version updates but to do a major version I need to put the app in maintenance mode, dump, restore, and swap to the new DB. It would be amazing if that could be automated with something like pglogical.
I particularly remember the mad flurry by "cloud distro" startups to capitalize on Heroku essentially shutting down their free tier last year. It's an infrequent thing but I think having a playbook for how to respond when a major competitor churns up their own users on a silver platter is super helpful for future reference.
anything you'd call out as particularly helpful to you in the "post heroku wars" period? looking for specific principles i can extrapolate to other similar situations
not complaining, innovation is good etc, but it doesnt come with out its costs to DX
I would have definitely proposed it to my company, but unfortunately the per-seat pricing is a no-go for us. We are having flexible teams, and we often change people per project or hire from contractors so the user management can quickly become a mess on per-seat projects.
We will end-up creating some shared accounts to save on costs, and it will become messy to manage, some people will be denied access,... so unfortunately we will need to pass.
What does Render bring to the table that's new?
AWS/GCS is not in the same space, they are a lot lower level. For someone like me I'd hate having to move to AWS/GCS, I just want to code my project locally, git push and it's live, no fumble with devops stuff. Also Firebase etc is a bit too high level for what I like, I still like to build the project locally and have it run on my computer fully.
In Heroku's defense, much of what we know and love them for was started before Salesforce acquired them, but then was accelerated and launched while under Salesforce. They just got very stagnant after a while and focused more on Salesforce integrations and that lately.
- Render
- Railway
- Northflank
- Fly
From easiest to hardest, in the sense of Heroku like to AWS like, I would scale them like so:
Heroku------------------------------AWS
Render Railway Northflank Fly
Render is definitely the easiest, most friendly and predictable of the four.I don't see how you would host a Phoenix project in Vercel.
Does anyone use Render at scale? I image the bills are hefty.
Im seeing a lot of startups using this word, why?? It sounds silly, like you're selling me a childrens toy? You're not delightful, its not a 50's musical number.
Its just the word dejour.