Generated by GPT-5-mini| Heroku | |
|---|---|
| Name | Heroku |
| Type | Cloud platform as a service |
| Industry | Software |
| Founded | 2007 |
| Founders | James Lindenbaum, Adam Wiggins, Orion Henry |
| Headquarters | San Francisco, California |
| Parent | Salesforce (2010–present) |
Heroku is a cloud platform as a service that enabled developers to build, run, and operate applications entirely in the cloud. Launched in 2007, it became known for abstracting infrastructure through dynos and buildpacks, attracting startups, enterprises, and projects across technology ecosystems such as Amazon Web Services, Google Cloud Platform, Microsoft Azure, Docker, and Kubernetes. Heroku's model influenced platform offerings from companies like Red Hat, IBM, Oracle Corporation, Pivotal Software, and DigitalOcean.
Heroku was founded in 2007 by James Lindenbaum, Adam Wiggins, and Orion Henry during an era defined by platforms such as RailsConf, O'Reilly Media, ACM SIGPLAN, and the rise of Ruby on Rails, which significantly shaped its initial focus. Early investments and partnerships involved firms and events like YC-adjacent accelerators, Benchmark-backed rounds, and interest from technologists at Facebook, Twitter, and LinkedIn. In 2010, Heroku was acquired by Salesforce at a time when Cloud Foundry, OpenStack, and VMware were expanding enterprise cloud strategies. Subsequent milestones intersected with initiatives from Amazon, Google, Microsoft, DockerCon, and standards discussions involving Cloud Native Computing Foundation and Linux Foundation affiliates. The platform's timeline featured shifts coinciding with product launches from GitHub, Bitbucket, Travis CI, and acquisitions by firms such as Zendesk and Twilio that altered developer toolchains across Silicon Valley and beyond.
Heroku's architecture used concepts such as dynos, buildpacks, slug compilation, and an ephemeral filesystem, integrating technologies and services allied with PostgreSQL ecosystems, Redis, Memcached, NGINX, HAProxy, Linux, and Amazon S3. Underneath, provisioning and orchestration related to technologies and projects like Docker, Kubernetes, HashiCorp Nomad, Consul, and Vault shaped operational conversations; enterprise integrations referenced Salesforce Platform, Heroku Connect, MuleSoft, and API Gateway patterns. Logging and monitoring workflows commonly tied into tools from Datadog, New Relic, Splunk, and Prometheus while CI/CD pipelines connected with Jenkins, CircleCI, GitLab CI, and Travis CI. Security and compliance discussions invoked standards and organizations such as SOC 2, ISO 27001, PCI DSS, and regulators including SEC and national agencies in European Union jurisdictions.
Heroku supported multiple language runtimes via buildpacks inspired by work from communities like Heroku Buildpack contributors, enabling deployment for runtimes with ecosystems including Ruby, Node.js, Python, Java, Scala, Clojure, PHP, and Go. Language ecosystems and package managers such as npm, Bundler, Maven, Gradle, pip, Composer, and Glide were integral to app compilation. Third-party and community buildpacks interfaced with services and frameworks like Rails, Sinatra, Express.js, Django, Flask, Spring Framework, Play Framework, Laravel, and Gin Gonic. Add-on marketplace integrations referenced offerings by Heroku Add-ons partners and vendors including SendGrid, Papertrail, New Relic, Redis Labs, and ClearDB, mirroring trends from AWS Marketplace and Google Cloud Marketplace.
Deployment workflows centered on Git-based workflows and integrations with version control and hosting platforms such as GitHub, Bitbucket, GitLab, SourceForge, and tools like Sublime Text, Visual Studio Code, and JetBrains IntelliJ IDEA. Developers used the Heroku CLI and git push/flavored deployment alongside CI/CD orchestrators from CircleCI, Jenkins, Travis CI, and GitLab CI/CD, often coupling with containerization by Docker and orchestration by Kubernetes. Collaboration and project management often referenced services like JIRA, Trello, Asana, and Slack, while testing and QA workflows involved frameworks and services such as RSpec, JUnit, pytest, Selenium, and BrowserStack. Observability and incident workflows linked to alerting stacks and practices advocated by PagerDuty, VictorOps, and incident postmortem traditions seen at Google SRE and Facebook Engineering.
Heroku's pricing and service tiers included free, hobby, professional, and enterprise plans, reflecting market models similar to those of AWS Free Tier, Google Cloud Free Tier, and Azure Free Account. Add-on pricing mirrored marketplace models exemplified by Salesforce AppExchange, AWS Marketplace, and vendor strategies from New Relic, Datadog, and Redis Labs. Enterprise offerings involved account management, compliance guidance, and integration services, comparable to packages from IBM Cloud, Microsoft Azure Stack, Oracle Cloud Infrastructure, and managed platform vendors like Pivotal (VMware Tanzu). Billing and contract negotiations often interfaced with procurement practices common at Fortune 500 firms, global consultancies such as Accenture, Deloitte, Ernst & Young, and system integrators including Capgemini.
Heroku drew praise from startups and developer communities associated with Y Combinator, TechCrunch, The New York Times, and industry analysts at Gartner for lowering operational complexity and accelerating time-to-market. Critics and commentators from outlets like The Register, Wired, Ars Technica, and bloggers from Hacker News and Medium raised concerns about vendor lock-in, cost at scale versus raw infrastructure providers (AWS, GCP, Azure), and the limitations of ephemeral filesystem design when compared to persistent storage paradigms promoted by Kubernetes and OpenEBS. Enterprise customers discussed migration narratives involving Cloud Foundry, Kubernetes, Docker Swarm, and managed services from Red Hat OpenShift and Google Kubernetes Engine; security incidents and operational outages prompted analysis in publications such as TechCrunch and reports by independent firms like 451 Research.
Category:Cloud computing platforms