Integrations/Heroku

Control what your AI agents do in Heroku.

Let your team build AI agents for Heroku. Bollard AI controls what each one can do, app by app.

Request early accessSee how it works →
Heroku
Deploy Agent
marketing-site AppOffReadFull use
api AppOffReadFull use
payments AppOffReadFull use
Deploy releases
What agents can do

Set what each agent can do in every app.

Each app gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see the app or that it exists.
Read
Read-only
The agent can read dynos, releases, and config in that app. It can't change anything.
Full use
Manage and update
The agent can scale dynos and update settings in that app.

Some actions stay off until explicitly turned on

Each one ships to production, removes an app for good, or exposes config, so it could override the limits set on individual apps.

Deploying releases to productionDeleting appsReading or changing config vars
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's Heroku a single time and chooses which apps it covers. Any app left out stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead, scale, and update settings in a single app
Example

A release management agent.

A deploy agent scales dynos on marketing-site and can read api, but it can't open the payments app or ship a release.

marketing-site AppOffReadFull use
api AppOffReadFull use
payments AppOffReadFull use

Manage access

ALLOWEDDeploy Agent scaled a dyno on marketing-site
ALLOWEDDeploy Agent read a release in api
BLOCKEDDeploy Agent tried to open the payments app, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and Heroku, so they never hold your Heroku keys and never reach Heroku directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to Heroku. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every app starts off-limits, and shipping to production is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your Heroku keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which app or release, and the decision. The record is readable and can't be edited after the fact.

Questions

Heroku, answered.

Does connecting Heroku hand Bollard AI all your apps?+
Only what's connected. An admin chooses which apps Bollard AI covers, and that sets the most any agent could reach. Bollard AI doesn't browse or copy your account. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent ship to production or read our secrets?+
Not unless you turn it on. Deploying releases and reading config vars are held off by default, so an agent can scale and read where you allow without ever shipping to production or touching secrets, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our Heroku keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches Heroku, and the blocked attempt lands in the activity record with the reason.
How do we connect Heroku?+
An admin connects the company's Heroku once. Bollard AI seals the connection and builds the list of apps to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in Heroku, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →