Categories

Heroku Architecture
- Compute (Dynos)
  - Dyno Management
  - Dyno Concepts
  - Dyno Behavior
  - Dyno Reference
  - Dyno Troubleshooting
- Stacks (operating system images)
- Networking & DNS
- Platform Policies
- Platform Principles

Language Support
- Node.js
  - Working with Node.js
  - Troubleshooting Node.js Apps
  - Node.js Behavior in Heroku
- Ruby
  - Rails Support
  - Working with Bundler
  - Working with Ruby
  - Ruby Behavior in Heroku
  - Troubleshooting Ruby Apps
- Python
  - Working with Python
  - Background Jobs in Python
  - Python Behavior in Heroku
  - Working with Django
- Java
  - Java Behavior in Heroku
  - Working with Java
  - Working with Maven
  - Working with Spring Boot
  - Troubleshooting Java Apps
- PHP
  - Working with PHP
  - PHP Behavior in Heroku
- Go
  - Go Dependency Management
- Scala
- Clojure
- .NET

Databases & Data Management
- Heroku Postgres
  - Postgres Basics
  - Postgres Getting Started
  - Postgres Performance
  - Postgres Data Transfer & Preservation
  - Postgres Availability
  - Postgres Special Topics
  - Migrating to Heroku Postgres
- Heroku Key-Value Store
- Apache Kafka on Heroku
- Other Data Stores

Monitoring & Metrics
- Logging

App Performance

Add-ons
- All Add-ons

Collaboration

Security
- App Security
- Identities & Authentication
  - Single Sign-on (SSO)
- Private Spaces
  - Infrastructure Networking
- Compliance

Heroku Enterprise
- Enterprise Accounts
- Enterprise Teams
- Heroku Connect (Salesforce sync)
  - Heroku Connect Administration
  - Heroku Connect Reference
  - Heroku Connect Troubleshooting

Patterns & Best Practices

Extending Heroku
- Platform API
- App Webhooks
- Heroku Labs
- Building Add-ons
  - Add-on Development Tasks
  - Add-on APIs
  - Add-on Guidelines & Requirements
- Building CLI Plugins
- Developing Buildpacks
- Dev Center

Accounts & Billing

Troubleshooting & Support

Integrating with Salesforce

Router 2.0 is now the default for all new Eco-tier Applications

Change effective on 20 March 2025

Router 2.0 is the new Common Runtime router, replacing the legacy router. It is now the default for all new Eco-tier applications. Basic, Standard and Performance-tier applications will continue to run on the legacy router until the tier-specific end-of-life date for the legacy router found in the link below.

See the Legacy Router end-of-life FAQ Help article for updates on timelines and information.

Ruby support for Bundler 1.x re-enabled until April 30th, 2025 Java 24 now available