Need advice about which tool to choose?Ask the StackShare community!
Heroku vs Stackato: What are the differences?
<Write Introduction here>
- Deployment Model: Heroku utilizes a public cloud deployment model, while Stackato offers both public and private cloud deployment options, providing more flexibility in hosting your applications.
- Pricing Model: Heroku operates on a pay-as-you-go pricing model, where you are charged based on your usage, while Stackato offers a subscription-based pricing model, allowing for more predictable costs.
- Language Support: Heroku primarily supports Node.js, Ruby, Java, PHP, Python, Go, Scala, and Clojure, while Stackato extends its support to additional languages like .NET, Perl, and more, catering to a wider range of developers.
- Customization and Control: Heroku simplifies the deployment process with its predefined buildpacks and limited configuration options, whereas Stackato provides greater customization and control over your deployment environment through its platform features.
- Scalability: Heroku offers automatic vertical scalability with its Dynos feature, but Stackato allows for horizontal and vertical scaling, giving you more flexibility in managing the growth of your applications.
- Security Features: Stackato places a strong emphasis on security by offering features like built-in multi-tenancy, role-based access control, and support for LDAP and Active Directory integration, compared to Heroku's more basic security measures.
In Summary, Heroku and Stackato differ in their deployment models, pricing structures, language support, level of customization and control, scalability options, and security features.
As I was running through freeCodeCamp's curriculum, I was becoming frustrated by Replit's black box nature as a shared server solution for Node app testing. I wanted to move into a proper workflow with Git and a dedicated deployment solution just for educational or non-commercial purposes. Heroku solved that for me in spades.
Not only does Heroku support free app deployment if you don't use their extra service handlers, but you can directly hook into your GitHub repos and automatically update the app whenever you commit to the main branch. It's a simple way to get an app running as fast as possible if you wish to share a proof of concept or prototype before moving to dedicated servers.
The Friendliest.app started on Heroku (both app and db) like most of my projects. The db on Heroku was on the cusp of becoming prohibitively expensive for this project.
After looking at options and reading recommendations we settled on Render to host both the application and db. Render's pricing model seems to scale more linearly with the application instead of the large pricing/performance jumps experienced with Heroku.
Migration to Render was extremely easy and we were able to complete both the db and application moves within 24 hours.
The only thing we're really missing on Render is a CLI. With Heroku, we could manage everything from the command line in VSCode. With Render, you need to use the web shell they provide.
I'm transitioning to Render from heroku. The pricing scale matches my usage scale, yet it's just as easy to deploy. It's removed a lot of the devops that I don't like to deal with on setting up my own raw *nix box and makes deployment simple and easy!
Clustering I don't use clustering features at the moment but when i need to set up clustering of nodes and discoverability, render will enable that where Heroku would require that I use an external service like redis.
Restarts The restarts are annoying. I understand the reasoning, but I'd rather watch my service if its got a memory leak and work to fix it than to just assume that it has memory leaks and needs to restart.
Pros of Heroku
- Easy deployment703
- Free for side projects459
- Huge time-saver374
- Simple scaling348
- Low devops skills required261
- Easy setup190
- Add-ons for almost everything174
- Beginner friendly153
- Better for startups150
- Low learning curve133
- Postgres hosting48
- Easy to add collaborators41
- Faster development30
- Awesome documentation24
- Simple rollback19
- Focus on product, not deployment19
- Natural companion for rails development15
- Easy integration15
- Great customer support12
- GitHub integration8
- Painless & well documented6
- No-ops6
- I love that they make it free to launch a side project4
- Free4
- Great UI3
- Just works3
- PostgreSQL forking and following2
- MySQL extension2
- Security1
- Able to host stuff good like Discord Bot1
- Sec0
Pros of Stackato
- Compliance - Owning the data helps with SOX, etc2
Sign up to add or upvote prosMake informed product decisions
Cons of Heroku
- Super expensive27
- Not a whole lot of flexibility9
- No usable MySQL option7
- Storage7
- Low performance on free tier5
- 24/7 support is $1,000 per month2
Cons of Stackato
Sign up to add or upvote consMake informed product decisions
What is Heroku?
What is Stackato?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Heroku?
What companies use Stackato?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Stackato?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+47
+39+25
+25+24
+20