Connect Heroku to Zed
Give Zed governed access to Heroku through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Heroku to Zed in four steps
Admins approve the server once. Everyone in Zed then gets it through the same governed connection.
- 1
Approve Heroku in Runlayer
Add Heroku from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Zed to Runlayer
Users add the Runlayer Plugin to Zed by following Runlayer’s setup guide. Zed reaches Heroku’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Zed setup guide - 3
Sign in to Heroku
An admin adds Heroku credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Heroku from Zed
Heroku’s approved tools appear in Zed. Every call is checked against policy and recorded.
Tools
Heroku tools in Zed
Heroku reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in Zed
Some controls apply to every client at the gateway. Others depend on what Zed exposes to Runlayer.
Gateway policy (available)
Every Heroku call from Zed passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Zed as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Zed yet, so control happens at the gateway.
Frequently asked questions
Connect more