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.
We have clarified what the "resources" are.
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.