Deep-dive on the Next Gen Platform. Join the Webinar!

Skip Navigation
Show nav
Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Visit the Heroku Blog

    Find news and updates from Heroku in the blog.

    Visit Blog
  • Log inorSign up
Hide categories

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
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • 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
      • PHP Behavior in Heroku
      • Working with PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .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
  • AI
    • Working with AI
  • 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
  • Extending Heroku
  • Building Add-ons
  • Add-ons Generation Compatibility Guide for Partners

Add-ons Generation Compatibility Guide for Partners

Last updated April 14, 2025

Table of Contents

  • Differences Between Cedar and Fir Generations
  • Test Your Add-on For Fir Compatibility
  • Enable Your Add-on to Support Fir
  • Additional Reading

This article covers how add-on providers handle and enable support for different Heroku Generations.

Differences Between Cedar and Fir Generations

Here are the differences between the generations of the Heroku platform that are relevant to add-on providers. To understand all differences between the generations, Heroku Generations.

Logging

Only Cedar supports add-ons writing to or accessing application logs.

If your add-on currently writes to application logs for Cedar-generation apps, but these logs aren’t a critical part of the add-on’s functionality, consider enabling support for Fir for the add-on while understanding this current logging limitation.

Heroku is working on new extensibility points for third-party add-ons to accept logs and additional telemetry from Heroku apps.

Buildpacks

The Fir generation uses Cloud Native Buildpacks (CNBs) instead of classic Heroku buildpacks. Classic buildpacks are not compatible with Fir. If an add-on relies on custom buildpacks for some of its functionality, you must use the equivalent CNBs for Fir-generation app support. If you created a custom classic buildpack you want to make a CNB equivalent of, see Creating Cloud Native Buildpacks from Classic Buildpacks.

Private Spaces and Regions

Cedar-generation apps can run on either Common Runtime or Private Spaces. Fir apps currently only exist in Private Spaces. See Supporting Private Spaces as an Add-on Partner for more info.

Test Your Add-on For Fir Compatibility

If you add-on uses one of the features listed under generational differences relevant to add-ons, test Fir compatibility with a separate staging or test add-on. Fir compatibility is at the add-on level and you can’t configure its support per plan.

Follow these steps to test add-on Fir compatibility:

  1. Create a test or staging add-on if you don’t already have one. Keep the test add-on in Alpha stage.
  2. Enable Fir support in the Marketplace Listing tab of the test add-on in the Heroku Partner Portal.
  3. Create a Fir space and a Fir app.
  4. Provision an instance of the test add-on to the Fir app.
  5. Validate that the test add-on works correctly when provisioned to a Fir app.
  6. When you’re ready, enable Fir support in the Marketplace Listing tab of the main add-on in the Partner Portal.

Enable Your Add-on to Support Fir

You can enable support for Fir in the Heroku Partner Portal in Settings tab for an add-on. You must enable support in the portal before users can install your add-on on Fir-generation apps. Ensure that you test for Fir compatibility first if your add-on uses one of the features listed under generational differences relevant to add-ons.

Additional Reading

  • Heroku Generations
  • Creating Cloud Native Buildpacks from Classic Buildpacks

Keep reading

  • Building Add-ons

Feedback

Log in to submit feedback.

What Is an Add-on? Add-on Terms of Use

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure
  • .NET

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices