**What the product does (objective value proposition)**
- **Heroku** is a managed **Platform-as-a-Service (PaaS)** used to build, deploy, run, and scale applications without directly managing underlying servers. Applications run in lightweight Linux containers called **dynos**. Official positioning emphasizes developer workflow, managed operations, and integration with Salesforce.
- Heroku is typically used for **web applications, APIs, background workers, and event/queue-based workloads**, and is commonly paired with managed data add-ons (e.g., Heroku Postgres, Redis) and third-party add-ons via the Elements Marketplace.
**Target market and market positioning**
- Historically common among startups, teams prioritizing rapid deployment, and polyglot development teams.
- In Salesforce’s positioning, Heroku is presented as a platform for building custom applications that integrate with Salesforce data and workflows (for example, using Heroku Connect).
- Market commentary indicates many larger enterprises standardize on AWS/Azure for governance and use Heroku selectively, typically when there is a Salesforce-centric integration requirement.
**Company background (founding year, HQ, leadership)**
- Heroku was founded in **2007** and was later acquired by Salesforce.
- Salesforce announced completion of its acquisition of Heroku in **January 2011**.
- Product leadership information for Heroku is not consistently consolidated on a single official page; public reporting in early 2026 referenced Salesforce SVP/GM **Nitin T. Bhat** in relation to Heroku’s roadmap status.
**Funding and growth (investment rounds, acquisitions, customer count/revenue)**
- Salesforce acquired Heroku; the acquisition was publicly disclosed at the time.
- Current, verifiable metrics for Heroku revenue or customer counts are not consistently disclosed publicly; procurement discussions generally require direct engagement with Salesforce for enterprise footprint details.
**Pricing model (tiers and costs, where available)**
- Heroku pricing follows a consumption-based model (dyno units/usage), with guidance on Salesforce/Heroku pricing pages and billing documentation.
- Official pricing pages describe dynos and list tiers; exact pricing and entitlements can vary by plan type, region, and contract. Verification of current prices and entitlements should occur on official pricing pages and in contract negotiations.
- Heroku Dev Center documents usage-based billing mechanics and the “max monthly price” behavior for dynos that run continuously.
- Industry/community commentary has noted baseline pricing examples and references to lower-cost plans introduced after the free tier retirement.
**Total cost of ownership (TCO) considerations**
- **Direct platform costs**: dynos (web/worker), managed data (Postgres/Redis), add-ons, logs/monitoring, private networking features, and compliance tiers (e.g., Shield).
- **Indirect costs frequently cited by users**:
- Add-on spend and cumulative add-on costs across multiple services.
- Higher platform costs at scale compared with self-managed approaches on AWS/GCP/Azure, particularly for steady 24/7 workloads.
- Migration costs if moving off Heroku (buildpack → Docker/Kubernetes migration, add-on replacement, and operational tooling replacement).
- **Operational savings**: Teams commonly justify Heroku by reduced DevOps effort and faster delivery cycles relative to building and operating equivalent infrastructure in-house.
**Key competitors (4–6 direct alternatives)**
- **Render**, **Fly.io**, **Vercel**, **Netlify**, **Google Cloud Run**, **AWS Elastic Beanstalk** (and, for more control, **ECS/Fargate** or **Kubernetes**).