Ryan Basayne of Coralogix sits down with Morgan Shultz of Copado to discuss his experience leveraging Coralogix on the Heroku Platform.

Copado is an end-to-end, native DevOps solution that unites Admins, Architects and Developers on one platform. DevOps is a team sport, and uniting all 3 allows you to focus on what you need to focus on - getting innovation into the hands of the customer.


Here at Xplenty, we have a number of customers who use Xplenty’s Heroku Add-on with Heroku Connect to enable Salesforce integration at their organization. Since Xplenty and Heroku Connect both provide a bi-directional data connection to Salesforce, you might think that you should use one or the other for your integration needs. But our experience shows that each tool has specific strengths that make them complementary parts of a full solution. Read on to understand the basics of our Xplenty solution, Heroku Connect, and how they can work together to address your Salesforce integration challenges.

Heroku Connect

Heroku Connect is a Salesforce component, built on the Heroku platform, that...


Yesterday we announced a major step towards making buildpacks a multi-platform, open standard by contributing to Cloud Native Buildpacks, a Sandbox Project hosted by the Cloud Native Computing Foundation. Today, we are announcing that you can now easily share your buildpacks with the world, by registering them with the Heroku Buildpack Registry.

As of this post, the Buildpack Registry contains over 100 buildpacks created by authors like you. Because of your contributions, Heroku developers can easily use languages and frameworks like Meteor, Elixir, and React in their applications. If you’ve created a custom buildpack and wish to share it with the community, visit Dev Center to learn...


Asynchronous provisioning allows add-ons to perform out-of-band provisioning in a first-class way. It’s intended for add-on services that need extended time to set up and help make automated app setup and orchestration easier and less error-prone.

The customer will be billed as soon as the add-on starts provisioning. This means the time and cost of provisioning your service is accounted for in how much a customer pays. As such, you should make every effort to provision expediently so customers get value from your service as quickly as possible.

Add-ons that take longer than 12 hours to provision (or those your service fails to mark as “provisioned” via the API in that time period) will be...


Need to quickly catch up on this past quarter's announcements? Here are the top three topics to tune in on:

The Platform API for Partners provides many official endpoints that allow you to introspect security settings, discover other customer instances of the same add-on, and much more. With the Platform API, add-ons have an OAuth client secret and a number of OAuth authorizations, one token per provisioned add-on; it is only used to authenticate requests to create the scoped tokens and not used to authenticate other requests to the Platform API.

Updated password requirements for the add-on manifest go into effect as of December 15, 2017. Add-on manifest password values are required...


Browse the archives for ecosystem or all blogs Subscribe to the RSS feed for ecosystem or all blogs.