There's so much you could do from a UX point of view. Nobody wants to be fiddling around with IAM roles, trying to add the right ingress rules so their server can actually connect to the internet, configuring TCP_NODELAY, etc - and then constantly wondering if their server is secure. Just to run some CRUD React app whose requirements are the same as the other 99.99% of developers.
It's not perfect, and there is probably a point in time for a project where you'll need to evaluate other options, but I haven't found much that's better for small-scale stuff if you don't want to think too hard.
If (devops hat on) you want baseline compute/storage, I think I could see running on Render long-term. Where I (speaking personally) get off the ride is when I start needing external stuff, and that's usually pronounced "AWS services". Stuff like SQS and SNS are still The Killer App for AWS for me, and while I was poking at Render for my most recent personal project, it was easier to put compute and data storage into Fargate/RDS and not have to think about multiple control planes.
A seamless, please-not-Terraform way to cross-manage Render resources with other cloud options would be pretty killer. (Which is directly in tension with the discussions of simplicity here. Turns out cloud stuff is hard.)
Thanks very much for the personal message. I'll set up a personal account and give it a spin. My company is a bit more nonchalant about vendor lock-in than I am, and so we're relying on certain AWS services for certain things, but we're also flexible and I'd be very keen to move some stuff onto a service like this.
On a more general note, I really hope you succeed. I believe 95% of developers just want to be able to:
- sign up
- get a machine with an IP(v4) addr
- [wanted/needed but not expected] have some help setting up / hooking up DNS + TLS
- get their application onto it somehow (in order of sophistication: 1: drag-a-folder, 2: shell access to use scp/rsync, 3: GitOps w/ a helpful flow)
- get it running and keep it running
- have some basic monitoring and alerting capacities
- have a sense of assurance that it's 'secure' (I know, this word is as meaningless as 'performant' without further qualification, but that doesn't matter)
I think you could get so far with a "sane defaults, maximally configurable if you wish" model. You may not support computational genomics or FPGA-assisted currency trading, but you can win 100x on UX by not having to play Twister trying to accommodate the long tail of niche users.
The only other bit of vague and cloudy fortune cookie advice I have to offer is: an escape hatch is so important. It's somehow reassuring to know that, if I want to do [thing I can do on AWS but not on Render], that there's some way - however fiddly - for me to connect the two, or replicate that thing. (Being necessarily vague here because I don't have anything particular in mind.)
Anyway - really appreciate your reply, and really appreciate your serving this market. (And please don't offer any credits or anything like that - I know it's common in these threads, but I'm really not fishing for that. We have a fuck ton of VC cash to spend, and I believe in sampling the pricing in the exact same way that I'd be sampling the functionality.)
I've been wanting to use render for a long time now at our startup, but last time I looked at your GDPR info it was lacking. We sell to public education institutes in the EU, so it is a make or break for us. We might not be your target customer in that case, but otherwise I would love to hear what is possible.
Edit: Apropos of "there's a point in time where you'll need to evaluate other options": I think a good selling point would be a well-designed flow for 'ejecting' to a self-hosted or AWS/GCP environment. Yeah, yeah, it's not good for lock-in, but by the exact same token it would be a strong selling point. Done well, you could assuage the "we may as well get it out of the way now" concerns by saying that you'll make it easier to set up shop on AWS.
Render's great for letting us just focus on the app. There are things I want them to improve, but I'm confident they'll get there eventually.
Some mild complexity in deploy (and it is mild, a render.yaml file in your repo's super easy) comes from having the options to actually do things, I think.
In other words, nearly every complaint in this thread about the cloud is solved with some experience in the cloud. There's a reason it's so ubiquitous, and that's because it really is pretty damn simple once you get the hang of it.
I've seen enough 500 line YAML files to disagree with you.
I use it to spin a Windows server, then connect to Steam, download a game server, download some mods from S3 and start the service.
The rules are in security groups. I add one Steam security group, and then another group for each game, and the machine has both of them at the same time.
When the machine is running, everything is one PowerShell script.
Using a Linux dev instance can only be even more simple.
Disclaimer: I work at Cloudflare.
The concept itself is generally portable with several services offering largely compatible implementations although there is more porting work than would be ideal.
As for standards/vendor lock-in concerns, I’m sure that will get resolved sooner rather than later.
Running under QEMU doesn't mean a server is managed.
Every usage of RDS or Dynamo I saw until now did not need scaling nor DBA outsourcing that AWS provides.
For me, Hetzner Cloud hits the sweet spot for side projects. And I use their bare metal servers to run high-volume websites.
P.S. Surprisingly, non-tech businesses are often offset by Hetzner rather than by crooks with registered office in Suntec Tower, Singapore that run their "managed" services on Aquia that runs on AWS.
It’s easy to ignore those because we add them piecemeal over time with custom servers, but it is a huge drag on productivity when you add it all up.
Not only that, but you now own these services. If they break, you have to stop working on your product to fix them. Moreover, when your DIY cloud runs into problems, you won't have the benefit of a wealth of knowledge on the issue (internet forums, chat rooms, hiring people, etc) and of course you won't have anyone you can pay for support.
You'll also want a couple of additional environments, and things are probably complex enough that it justifies some infrastructure as code so you can (more or less) stamp out these environments and keep them in sync with your production environment (and also so you can rebuild prod in case of catastrophic failure).
You can definitely get there if you're using your own machines, but a PaaS or cloud provider will get you there a lot faster.
Most startups are not hard tech problems, despite the very strong desire to make them so by a technical founder.
You can even have manually provisioned instances, but you easily spin servers in multiple availability zones and have a load balancer in front of them. Similarly you can easily setup and maintain a database in multiple availability zones without much effort.
Have you really spent a similar amount of time learning your way around deploying applications on the cloud as you have administrating your own server?
It takes us some time to set up dedicated machines, but less than a day. Ansible helps a bunch.
The closest thing I can tease out of this claim that seems like a significant practical criticism is that you need a resilient communications channel for talking from, say, core logic to an email sender--but you need that on one node too, if you aren't using a the right datastore for the job you're asking to staple your hand to your face no matter how many nodes your application runs on.
And these days it's pretty trivial to use a lot of AWS free tier stuff--or other clouds, but let's be real, AWS gives you A Lot--for much of what you describe. CloudFront is not my favorite CDN but they give you a bonkers amount of free transfer these days. DynamoDB as an object cache, if you don't want to pay for Redis. SQS is free to like a million API request a month and you can stick a lambda on the other end of it to handle offline/async tasks. And SES turns email sending into an API call.
If your concern is velocity, then cloud stuff is almost unassailable. If your concern is price, better cloud stuff is hard to beat, too. If your concern is portability, I hope you're already profitable and that it's worth your time to worry about it.
So I am going back and seeing what else is possible. I tried setting up a PostgreSQL Compute VM but then I needed another specialized instance to act as a go between for allowing access for serverless vpc access. I get charged a bit for everything. I just want to build a product and see if people want it. I have no idea what to charge because I don't understand the costs. Do I spend time figuring out the costs of every little thing that is touched or do I install something on a hosted server?
I feel like there should be out of the box setups for this stuff in Google cloud. They have so much to offer, I think tying it together in easy to use and price packages would get a lot of people using it who need to rapidly get something made.
This is a big driver for the adoption of any tech - internal teams want to gain specific skills and job titles in order to get paid more somewhere else. I know that sounds cynical but as an engineer this has often been at the back of my mind when choosing technologies - either personally, or as a sweetener to get buy in from other engineers on some architectural choice I know they would otherwise object to.
After all, the director of engineering also wants to put "moved operations to the cloud" on their resume so they can get a better paying job somewhere else or a better title.
It's perfectly possible to build a MVP using a single VM and rsynched PHP code. The iteration speed (when solo) and amount of control is probably higher than anything you're referencing to.
In the end what matters the most if what technologies you're already familiar with.
Honestly reinventing the wheel like that to cut costs points to a management/vision issue. The founders should simply raise more money. The cloud is an incredible value proposition when you understand the amount of momentum and time it affords to an organization.
And, for larger companies, it also bypasses internal IT when the team just needs resources right now to innovate.
It’s true: You can set up and maintain all of your own services, create a backup system for them, test it all, and handle your own redundancy. If you have an engineering background, this probably feels natural and will feel like a lot of progress and accomplishment. But in the time it takes to do all of that (usually distributed and interwoven into other activities) you could have been prototyping out your startup. That’s the value of cloud.
You can always invest the effort into setting up your own services later as a cost reduction move. Doing the cost-reduction activities before you’ve even prototyped a business isn’t a great use of precious time in a startup’s early days.