It's challenging to cover every case when the surface area is as large as AWS. I picked the one that made me want to make this feature for Railway and shared it.
Even still:
- You can't use NPM when writing from the Lambda editor
- Deploying a function to a VPC w/ DB permissions is still a major challenge. If you go with click ops, you will be clicking for >10 minutes if you know what you're doing. If you mess up and want to start over, you will be stuck waiting for the Lambda's networking to teardown, sometimes longer than 20 minutes.
Thanks for clarifying. Of those you can 1-click deploy Git-based and Docker-based apps except Docker Compose, since containers are deployed to an ECS cluster. Self-hosted databases are out of scope for what we're trying to do. We're focused instead on making it dead simple to integrate with AWS-managed resources (via resource RBAC, network rules).
Not at the moment unfortunately. I understand it's more friction, but you can just clone any of those repos and deploy them to FlexStack in 1-click by linking your GitHub account.
Thanks for the feedback! I appreciate your honesty and your willingness to share.
> The "explainer" video is trying very hard to be cool
I have been working on a Loom version. Before putting a lot of time into the demo, I wanted to validate that people were watching it (and they are). I quickly put something together in iMovie that would introduce the product in <1 minute, was not trying to be cool. It stings to hear, but I accept that was the vibe.
> it's very busy and information dense ... nothing on the home page gives me enough detail
It has ~the same number of words as Render/Coolify/Vercel, so I will take your point that I'm not yet telling the story as well.
Shameless plug but I built https://flexstack.com for similar reasons. I wanted a Render/Vercel alternative on my own AWS account and all of the other options either didn't go far enough or were way too expensive for someone bootstrapping.
It's doubtfully about need. Why did they use it? Probably because they have a solid workflow already based on a React tool chain - so why not? In that case you could similarly ask, why go out of their way to create a static page if they use React for everything else and it's how their programmers are used to thinking? You can use whatever you want as long as it gets the job done. It's about comfort zones and preference.
Even still:
- You can't use NPM when writing from the Lambda editor
- Deploying a function to a VPC w/ DB permissions is still a major challenge. If you go with click ops, you will be clicking for >10 minutes if you know what you're doing. If you mess up and want to start over, you will be stuck waiting for the Lambda's networking to teardown, sometimes longer than 20 minutes.
Thus, I think it's a fair enough comparison.