Skip to Content
ResourcesIntegrationsDeveloper ToolsFly.io

Fly.io

Service domainCODE SANDBOX
Fly.io icon
Arcade OptimizedBYOC

Arcade tools designed for LLMs to interact with Fly.io

Author:Arcade
Version:1.0.2
Auth:No authentication required
30tools
30require secrets

Fly.io Toolkit

An Arcade toolkit that lets LLMs manage Fly.io infrastructure — apps, Machines, volumes, networking, TLS certificates, secrets, and deployments — via the Fly.io API.

Capabilities

  • App & release management: list, inspect, and deploy apps; roll out new container images; browse release history scoped to any organization.
  • Machine lifecycle: create, start, stop, restart, and destroy individual Machines; scale Machine count up or down; resize VM compute and memory.
  • Storage & networking: create, extend, and destroy persistent volumes; allocate and release dedicated IP addresses; list all assigned IPs including shared IPv4.
  • TLS certificates: add custom-domain certificates, retrieve required DNS validation records, check validation status, list, and remove certificates.
  • Secrets & config: set and unset app secrets with optional immediate rollout; list secret names (values are never returned by Fly.io).
  • Observability & discovery: read recent app logs (requires a token with explicit log-read access; returns a no_access status rather than raising when access is absent); list organizations, regions, and Machines with pagination metadata.

Secrets

FLYIO_ACCESS_TOKEN — A Fly.io personal access token or deploy token used to authenticate every API call. To create one, log in to the Fly.io dashboard, navigate to Account → Access Tokens, and generate a new token. For full infrastructure management, the token needs broad API access. For log reading specifically (Flyio.GetLogs), the token must additionally have log-read access granted; a token without it will cause that tool to return a no_access result rather than raising an error. Fly.io also supports scoped deploy tokens per-app, which are suitable for deployment-only workflows but will lack permissions for organization-level or cross-app operations.

See the Arcade secrets guide for how to store and reference secrets in Arcade, or manage them directly at https://api.arcade.dev/dashboard/auth/secrets.

Available tools(30)

30 of 30 tools
Operations
Behavior
Tool nameDescriptionSecrets
Add a TLS certificate for a hostname and return the DNS records to set.
1
Allocate a new IP address for an app.
1
Check a certificate's validation status and any pending DNS records.
1
Create a new Machine for an app from a container image.
1
Create a new persistent volume for an app.
1
Roll a new container image out to all of an app's Machines.
1
Permanently destroy a Machine. Stop it first unless force is set.
1
Permanently destroy a volume and the data it holds.
1
Grow a volume to a larger size. Volumes cannot be shrunk.
1
Get the current status of a single Fly.io app.
1
Read recent historical log entries for an app, optionally filtered. Reading logs requires a token granted log-read access, which is a capability separate from app management; a token without it cannot read logs at all. When that access is missing this returns a ``no_access`` result rather than raising, so prefer branching on the result's ``status`` over assuming logs are present.
1
Get the configuration, state, and health of a single Machine.
1
List Fly.io apps, optionally scoped to a single organization. Apps are returned in Fly.io's own ordering, with pagination metadata so a caller can tell when more apps exist beyond the returned window.
1
List the custom-domain TLS certificates configured on an app.
1
List the IP addresses assigned to an app, including the shared IPv4.
1
List the Machines that belong to an app.
1
List the Fly.io organizations the configured token can access.
1
List the Fly.io regions available for deploying apps and volumes.
1
List an app's release history, newest first.
1
List an app's secret names. Secret values are never returned by Fly.io.
1
List the persistent volumes that belong to an app.
1
Release a dedicated IP address so it is no longer assigned to the app.
1
Remove a custom-domain TLS certificate from an app.
1
Restart a Machine and report its settled state.
1
Scale an app to a target Machine count by adding or removing Machines.
1
Page 1 of 2(25 of 30)
Last updated on