Connect Heroku to Glean
Give Glean governed access to Heroku through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Heroku to Glean in four steps
Admins approve the server once. Everyone in Glean 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 Glean to Runlayer
Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Heroku’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Glean 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 Glean
Heroku’s approved tools appear in Glean. Every call is checked against policy and recorded.
Tools
Heroku tools in Glean
Heroku reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in Glean
Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.
Gateway policy (available)
Every Heroku call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.
OTLP telemetry (available)
Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.
In Glean
- Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.
Frequently asked questions
Connect more