Dashboard
← All integrations
Fly.io

Fly.io. Machines, volumes, and global edge deployments.

Connect your Fly.io account to let agents monitor your machines, volumes, and global deployments. Agents can check app health, analyze regional performance, and help manage your distributed infrastructure.

Join the waitlist

What Polylane does with Fly.io.

The whole fleet in one graph

Every app with its machines, volumes, certificates, and secrets, next to whatever else you run on other clouds.

Every region at once

Your machines run wherever your users are; your attention can't. Agents see the whole fleet, so one bad region stands out against the ones that are fine.

Detection without alert rules

Agents comb app and machine metrics and logs on a cadence and judge them against how each app normally behaves.

History for a fleet that churns

Machines deploy, stop, start, and move. Each sync records what appeared, changed, or disappeared, so investigations start from the change.

How it works.

01

Connect

Paste a read-only API token, the most restrictive type Fly offers. It's encrypted before it's stored, and the agent never sees it.

02

Sync

Apps, machines, and volumes land in the graph with their regions and history.

03

Agents take the watch

The fleet is watched in every region at once, and investigations don't wait for your timezone.

In the graph.

The Fly.io resource types Polylane syncs, with their edges, config, and history.

Fly App
Machine
Volume
Certificate
Secret

The tools agents get.

What an agent can do with Fly.io mid-investigation. Every call lands in the thread transcript, cited.

flyApi

Call any Fly.io Machines REST endpoint that lacks a dedicated tool

flyListReleases

List release history for a Fly.io app

flyQueryMetrics

Query Fly.io Prometheus metrics for an app

flyGetLogs

Get logs for a Fly.io app via Prometheus metrics

Questions.

Is Polylane an AI SRE for Fly.io?

It's what most people mean by the term: agents that keep your Fly.io resources in one context graph, watch them, investigate issues and fix what they can, with a human approving anything that changes production. We call it self-operating software rather than an AI SRE: the point is that your software looks after itself, not that a bot joins the on-call rotation.

Can Polylane change anything in Fly.io?

Only if you let it. Connected read-only, agents investigate and explain, and changes only ever land as pull requests for you to review. With write access, every write pauses for your approval first, with the method, path and reason on screen. Rollbacks are off by default: you enable them per automation and can turn them off at any time.

Connect it once. Agents take it from there.