Control what your AI agents do in Render.

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

Render
Deploy Agent
web ServiceOffReadFull use
worker ServiceOffReadFull use
api ServiceOffReadFull use
Deploy to production
What agents can do

Set what each agent can do on every service.

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

Off
No access
The agent can't see the service or that it exists.
Read
Read-only
The agent can read deploys and settings for that service. It can't change anything.
Full use
Manage and update
The agent can update settings on that service.

Some actions stay off until explicitly turned on

Each one changes what is live, removes a service for good, or exposes its config, so it could override the limits set on individual services.

Triggering production deploysDeleting or suspending servicesChanging environment variables
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 Render a single time and chooses which services it covers. Any service 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 and update settings on a single service
Example

A deploy management agent.

A deploy agent updates the web service and can read worker, but it can't open the api service or deploy to production.

web ServiceOffReadFull use
worker ServiceOffReadFull use
api ServiceOffReadFull use

Manage access

ALLOWEDDeploy Agent updated the web service
ALLOWEDDeploy Agent read a deploy in worker
BLOCKEDDeploy Agent tried to open the api service, 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 Render, so they never hold your Render keys and never reach Render directly.

Everything runs through Bollard AI

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

Denied by default

Every service starts off-limits, and deploying 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 Render 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 service or deploy, and the decision. The record is readable and can't be edited after the fact.

Questions

Render, answered.

Does connecting Render hand Bollard AI all your services?+
Only what's connected. An admin chooses which services 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 deploy to production or delete a service?+
Not unless you turn it on. Triggering production deploys and deleting or suspending services are held off by default, so an agent can update and read where you allow without ever changing what is live, 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 Render 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 Render, and the blocked attempt lands in the activity record with the reason.
How do we connect Render?+
An admin connects the company's Render once. Bollard AI seals the connection and builds the list of services 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 Render, without the risk.

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