github.com/dahs81/otto@v0.2.1-0.20160126165905-6400716cf085/website/source/intro/vs/heroku.html.md (about)

     1  ---
     2  layout: "intro"
     3  page_title: "Otto vs. Heroku"
     4  sidebar_current: "vs-other-heroku"
     5  description: |-
     6    Comparison between Otto and Heroku.
     7  ---
     8  
     9  # Otto vs. Heroku
    10  
    11  Heroku is a platform for deploying just about any kind of application.
    12  Heroku manages the underlying infrastructure, and provides easy knobs
    13  for scaling up and down. Heroku addons allow applications to easily
    14  talk to external services such as databases, queues, etc.
    15  
    16  Heroku provides no solutions for development environments. Heroku can only
    17  deploy to their infrastructure (which is on AWS for now, but you don't have
    18  direct access to the underlying infrastructure).
    19  
    20  Otto aims to replicate the ease of Heroku deploys on any infrastructure
    21  while also providing a complete development experience. Otto can integrate
    22  more easily with custom services and custom infrastructure components that
    23  may not fit easily within the Heroku model.
    24  
    25  Additionally, the price of Heroku rises dramatically, very quickly becoming
    26  unaffordable for hobbyists and even startups. Otto itself is of course free,
    27  and it has multiple options for infrastructure flavors to balance cost.
    28  It is certainly cheaper than Heroku.
    29  
    30  Admittedly, the deployment experience with Otto is still not as clean
    31  and simple as Heroku, but for an initial release it is close. As time goes
    32  on, the Otto deployment experience will only get better. Otto's development
    33  experience is already fantastic.