Integrations/Fly.io

Control what your AI agents do in Fly.io.

Let your team build AI agents for Fly.io. Bollard AI controls what each one can do, area by area.

Request early accessSee how it works →
Fly.io
Infra Agent
Apps Account areaOffReadFull use
Machines Account areaOffReadFull use
Volumes Account areaOffReadFull use
Delete apps and machines
What agents can do

Set what each agent can do across your account.

Each area of Fly.io, like apps, machines, or volumes, gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see that part of your account.
Read
Read-only
The agent can read apps and machine status in that area. It can't change anything.
Full use
Create and update
The agent can create and update resources in that area, like an app.

Some actions stay off until explicitly turned on

Each one removes running infrastructure or data for good, so it could override the limits set elsewhere.

Deleting apps or machinesDeleting volumesSuspending running machines
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 Fly.io a single time. Bollard AI lays out the areas of your account, and anything you don't allow 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, create, and update resources in a single area
Example

An infrastructure agent.

An infra agent creates apps and can read machine status, but it can't delete volumes or suspend running machines.

Apps Account areaOffReadFull use
Machines Account areaOffReadFull use
Volumes Account areaOffReadFull use

Manage access

ALLOWEDInfra Agent created a record in Apps
ALLOWEDInfra Agent read a record in Machines
BLOCKEDInfra Agent tried to open Volumes, 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 Fly.io, so they never hold your Fly.io keys and never reach Fly.io directly.

Everything runs through Bollard AI

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

Denied by default

Every area starts off-limits, and removing running infrastructure 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 Fly.io 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 machine, and the decision. The record is readable and can't be edited after the fact.

Questions

Fly.io, answered.

Does connecting Fly.io hand Bollard AI your whole account?+
Only the areas you allow. An admin connects your Fly.io, and you decide which areas, like apps or machines, each agent can 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 delete our running infrastructure?+
Not unless you turn it on. Deleting apps, machines, and volumes is held off by default, so an agent can create and read where you allow without ever tearing down running infrastructure, 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 Fly.io 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 Fly.io, and the blocked attempt lands in the activity record with the reason.
How do we connect Fly.io?+
An admin connects the company's Fly.io once. Bollard AI seals the connection and lays out the areas of your account 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 Fly.io, 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 →