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

    Heroku Blog

    Find out what's new with Heroku on our 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
      • Node.js Behavior in Heroku
      • Troubleshooting Node.js Apps
    • 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
    • Model Context Protocol
    • Vector Database
    • Heroku Inference
      • Inference Essentials
      • AI Models
      • Inference API
      • Quick Start Guides
    • 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
  • Becoming an Add-on Partner

Becoming an Add-on Partner

English — 日本語に切り替える

Last updated April 25, 2024

Table of Contents

  • Building an Add-on
  • Heroku Partner Portal
  • Technical implementation

To effectively market your product to the Heroku community, you must be familiar with the basic Heroku user experience. If your team is new to the Heroku platform, we highly recommend you walk through the core concepts of creating and deploying an application on Heroku to understand the experience your future add-on customers expect.

Next, read about how your service interacts with the Heroku platform.

After completing the tour, you’re ready to start the technical integration of your add-on service. To help guide you along, there’s a step-by-step tutorial and several code examples.

Finally, review the business terms contained in the salesforce.com License and Distribution Agreement for the Heroku Elements Marketplace.

Building an Add-on

One of the key goals of the add-on program is to make the experience of building add-ons as easy as possible. We’ve made sure that it’s an open playground to experiment on. There’s no registration or setup required to start building an add-on. In many cases, a day or two is all that is needed to produce a working add-on.

Help is available in the Dev Center, and see Getting Support as an Add-on Partner to get in touch with us.

Heroku Partner Portal

The Partner Portal gives you a single place to manage your add-ons and your relationship with Heroku.

For new add-on partners, the Partner Portal offers instructions on how to build your add-on and submit it to Heroku. For current add-on partners, the Partner Portal serves as a place to manage all aspects of your add-on. Sections of the portal include:

  • Marketplace Listing: update your add-on’s listing in the Elements marketplace
  • Features & Plans: create and update your add-on plans and pricing
  • Reports: download monthly revenue reports
  • Logs: get visibility on issues your customers could be experiencing with your add-on
  • Company: update company information or add users
  • Settings: update settings for your add-on or view OAuth credentials
  • Next Steps: complete tasks to progress your add-on to beta, GA, and beyond

Partner Portal

Registering

Before you can use the Partner Portal or submit your add-on to the Heroku Elements marketplace, you must register on our Partner Portal as a Heroku Elements marketplace add-on partner. All that’s required to do is review the applicable agreements and policies, and then register for a Heroku account.

If you already have an existing Heroku account, log in with your existing credentials. If not, sign up for a new account. Your access to and use of the Partner Portal is governed by the salesforce.com License and Distribution Agreement for the Heroku Elements Marketplace, and if you’re domiciled in Italy, the Additional Terms for Heroku Elements Marketplace Providers. The purpose of the salesforce.com License and Distribution Agreement for the Heroku Elements Marketplace is to set up the business relationship between your company and Heroku. It covers the following:

  • Distribution of your product via the Heroku Elements Marketplace.
  • Intellectual property protection for both parties.
  • Revenue sharing terms, including payments, reporting, and audits.
  • Rules for pricing changes.
  • Confidentiality, allowing your company and Heroku to share details about upcoming product features, usage metrics, and so on.
  • Technical support and marketing responsibilities.

Be sure to familiarize yourself with the terms and conditions of the applicable agreements and policies before signing up.

Technical implementation

You must build or integrate your service with Heroku to become an add-on partner. For more information, see Building an Add-on.

Keep reading

  • Building Add-ons

Feedback

Log in to submit feedback.

What Is an Add-on? Bringing an Add-on to Market

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