I'm a long time user of Heroku, have built on top of it as a developer, CTO, etc.
My gut feeling from reading your homepage is that you're automating a lot of AWS service deployments on my behalf, but not "obfuscating" it that much from me either.
Your pricing talks about "Resources" which I assume are either AWS services or instances of those services. The free plan says that a REST api needs 40 resources which seems... like a lot? Is 40 good? bad? :-)
Heroku specifically allows you to think of your app == 1 dyno (depending on how much you scale it obviously), not 40 services.
I also note that the $290/month team plan talks about unlimited resources but doesn't specify their size/capacity. Heroku has sort of t-shirt sized tiers for dynos (and addons as well, like Postgres). What size of resources are you deploying on my behalf?
I do see the value of what you're doing, I'm just not getting a "as easy as Heroku" feeling. It seems potentially more powerful, but also raw-er i.e. this is automated AWS (that I might need to care for / understand), not... "git push heroku master" :-)
Every application (stack) deployed by Stacktape consists of multiple underlying AWS services (resources). For example a database instance, IAM role, auto-scaling policy, log group or a VPC subnet.
Stacktape does not limit the size/capacity (e.g. CPU, memory, GPU type or disk size) of the resources. You can use anything supported by AWS.
Also, the "git push heroku master" is similar to "stacktape deploy --stage production --region us-east-1".
The difference is that Stacktape can run on your system or on any CI/CD service and requires a (very simple) configuration.
I do understand that Stacktape might feel like it's not "as easy as Heroku". But what you trade in terms of simplicity, you get back 10 times in terms of control, flexibility and price reduction.
My gut feeling from reading your homepage is that you're automating a lot of AWS service deployments on my behalf, but not "obfuscating" it that much from me either.
Your pricing talks about "Resources" which I assume are either AWS services or instances of those services. The free plan says that a REST api needs 40 resources which seems... like a lot? Is 40 good? bad? :-)
Heroku specifically allows you to think of your app == 1 dyno (depending on how much you scale it obviously), not 40 services.
I also note that the $290/month team plan talks about unlimited resources but doesn't specify their size/capacity. Heroku has sort of t-shirt sized tiers for dynos (and addons as well, like Postgres). What size of resources are you deploying on my behalf?
I do see the value of what you're doing, I'm just not getting a "as easy as Heroku" feeling. It seems potentially more powerful, but also raw-er i.e. this is automated AWS (that I might need to care for / understand), not... "git push heroku master" :-)