View categories

Categories

Language Support
- Node.js
- Ruby
  - Working with Bundler
  - Rails Support
- Python
  - Background Jobs in Python
  - Working with Django
- Java
  - Working with Maven
  - Java Database Operations
  - Java Advanced Topics
  - Working with Spring Boot
- PHP
- Go
  - Go Dependency Management
- Scala
- Clojure

Databases & Data Management
- Heroku Postgres
  - Postgres Basics
  - Postgres Getting Started
  - Postgres Performance
  - Postgres Data Transfer & Preservation
  - Postgres Availability
  - Postgres Special Topics
- Heroku Data For Redis
- 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)
- Compliance

Heroku Enterprise
- Private Spaces
  - Infrastructure Networking
- 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

Upcoming changes to OAuth access tokens

Change effective on 07 March 2024

Starting April 1, 2024, we’ll prefix all newly granted Heroku OAuth access tokens with HRKU-.

Current token example: "57dce771-afad-4c41-a8a5-d10b7fbc743c"
Prefixed token example: "HRKU-57dce771-afad-4c41-a8a5-d10b7fbc743c"

Token behavior remains the same. All current tokens will continue to work and remain unchanged until they’re regenerated. This change allows us to enable additional security features in the future.

Node.js 21.7.0 now available New Heroku Postgres Essential-tier plans (Public Beta)