The Magic of `git push heroku master`
To understand the debate, you have to understand the magic. Before Heroku, deploying a web application was a nightmare of manual server configuration, arcane commands, and late-night troubleshooting. Heroku, founded in 2007, changed everything with a single,
elegant command: `git push heroku master`. A developer could push their code, and Heroku would handle the rest—provisioning servers, managing databases, and scaling traffic. It was a Platform as a Service (PaaS) that prioritized an almost supernatural developer experience (DevEx). This period is the undisputed golden age. On this, nearly every engineer agrees: early Heroku felt like the future. It allowed a generation of developers, startups, and hobbyists to bring ideas to life in hours, not weeks.
The Billion-Dollar Acquisition
The first major point of contention arrived in 2010 when Salesforce acquired Heroku for $212 million in cash. At the time, it was seen as a massive win—a validation of the developer-first model. But in hindsight, senior engineers are divided. One camp argues this was the beginning of the end. Heroku’s DNA was about serving individual developers and nimble startups, while Salesforce's universe revolved around large, slow-moving enterprise clients. They believe the acquisition inevitably placed Heroku on a path toward corporate bloat and away from its innovative roots. Another camp offers a more pragmatic view: the acquisition was a necessary lifeline. Heroku was burning cash and competing against the burgeoning cloud giants (AWS, Google Cloud, Azure). They contend that without Salesforce's deep pockets, Heroku might have simply faded into obscurity, unable to finance its own infrastructure.
Innovation Stagnation vs. Enterprise Integration
The post-acquisition decade is the heart of the disagreement. Critics point to a perceived innovation freeze. While the rest of the cloud world exploded with new services like serverless functions and container orchestration (e.g., Kubernetes), Heroku’s core offering seemed to evolve at a glacial pace. Pricing remained high compared to competitors, and features that developers craved were slow to arrive. To these engineers, Heroku became a “managed decline,” a cash cow milked by a parent company that didn’t understand its core audience. The counter-argument, often voiced by those with enterprise experience, is that the work was happening behind the scenes. Heroku was being integrated into the Salesforce ecosystem, a complex and enormously profitable endeavor. The focus shifted from shiny new toys for indie developers to compliance, security, and stability—the less glamorous but essential features required by Fortune 500 companies. From this perspective, Heroku wasn't stagnating; it was maturing into a serious enterprise tool.
The End of the Free Tier
The simmering debate boiled over in late 2022 when Heroku announced the end of its popular free tiers. For over a decade, these free plans had been the entry point for countless developers, students, and bootcamps. It was Heroku’s most powerful marketing tool and a symbol of its developer-first ethos. For many engineers, this move was the final betrayal. It signaled that Heroku was officially done catering to the community that built its legend, choosing instead to focus exclusively on paying customers. It broke the magical onboarding ramp that had created so much goodwill. However, other, more business-minded engineers saw it as an inevitable and logical step. The free tier was reportedly rife with abuse (crypto-mining, bots) and represented a significant operational cost. In an environment of economic tightening, they argue it was a sound business decision to shed a costly, non-revenue-generating service and focus on the core product for paying clients.
