agent safety

Agent safety answer

flyctl deploys and manages Fly.io applications and infrastructure.

Credential access

Reads Fly tokens, app config, secrets, and environment variables.

Remote mutation

Can deploy, scale, destroy, and change remote app state.

Publish/artifact risk

Publishes application images and release configuration.

Recommended control

Gate deploy, secrets, scale, destroy, and token commands.

Agent-use guidance

Allow status and config reads; require approval for deploys, secret changes, and destructive operations.

install

Additional install commands

macOS

Homebrewverified · 100%

brew install flyctl

local Homebrew formula metadata

MacPortsverified · 94%

sudo port install flyctl

MacPorts ports tree · devel/flyctl/Portfile · source: api.github.com

Linux

Nixverified · 92%

nix profile install nixpkgs#flyctl

nixpkgs package indexes · pkgs/by-name/fl/flyctl/package.nix · source: api.github.com

openSUSE zypperverified · 92%

sudo zypper install fly

openSUSE Tumbleweed package metadata · fly · source: download.opensuse.org

Windows

Chocolateyverified · 92%

choco install flyctl

Chocolatey community package catalog · flyctl · source: community.chocolatey.org

Scoopverified · 92%

scoop install main/flyctl

Scoop official bucket manifest trees · bucket/flyctl.json · source: api.github.com

Windows Package Managerverified · 92%

winget install --id Fly-io.flyctl -e

Windows Package Manager source index · Fly-io.flyctl · source: cdn.winget.microsoft.com

overview

Package summary

Command-line tools for fly.io services

Project links

Commands and aliases

fly
flyctl

history

Project history and usage

flyctl is the official Fly.io command-line interface, installed locally and invoked as fly to create, deploy, and manage applications on Fly.io.

Project history

Fly.io documentation presents flyctl as one of the primary ways to interact with the Fly.io platform. The CLI covers account login, app launch and deployment, Machines, volumes, networking, certificates, logs, secrets, organizations, SSH, WireGuard, and related platform operations.

The public superfly/flyctl repository is the source-control home for the CLI and has been released as a versioned Go command-line tool since early public releases in 2019.

Adoption history

flyctl adoption follows Fly.io's platform adoption: it is the documented entry point for launching apps, deploying services, managing infrastructure primitives, and automating CI workflows. Official install docs include Homebrew on macOS, shell install scripts on Unix-like systems, and a PowerShell installer on Windows.

How it is used

Users run fly auth login or signup, fly launch, fly deploy, fly logs, fly status, fly secrets, fly machine, fly volumes, fly certs, and related commands to manage apps and infrastructure from local terminals or CI jobs.

Why package nerds care

flyctl is package-nerd significant as a fast-moving cloud CLI: package managers need to track frequent upstream releases, expose both fly and flyctl entry points, and preserve a simple install path for users who bootstrap deployments from a fresh workstation or CI image.

It is also a good example of modern PaaS packaging, where the CLI is not just a helper but the main control plane surface for app creation, deployment, credentials, and operational introspection.

Timeline

2019: flyctl v0.0.1 was published.
2020: flyctl continued through frequent v0.0.x releases as Fly.io's CLI matured.
2022: Fly Machines and related infrastructure commands became part of the CLI surface.
2026: Fly.io documentation lists flyctl as the primary local CLI for apps, Machines, volumes, networking, and more.

Related projects

Fly.io Machines, Fly Launch, Fly Deploy, LiteFS Cloud, Managed Postgres, WireGuard networking, and Tigris storage are platform areas exposed through flyctl commands.
The Fly.io docs site and the superfly/flyctl GitHub repository are the main related official project surfaces.

Sources

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for flyctl. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 6 platform targets.
Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: ~/.fly/config.yml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: ~/.fly/config.yml

executables

Installed executables

Command	Kind	Exposure	Note
`fly`	cli	global executable
`flyctl`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version0.4.67

manager updated2026-07-06

local dataok

upstreamnot checked

latest detectednot detected

https://github.com/superfly/flyctl

infoNo cached GitHub release or tag data was available.https://github.com/superfly/flyctlnone confidence

install metadata

Package metadata

Package key	brew:flyctl
Version	0.4.67
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/flyctl
Homepage	https://fly.io
Repository	https://github.com/superfly/flyctl
Upstream docs	https://fly.io/docs
License	Apache-2.0
Source archive	https://github.com/superfly/flyctl.git
Last updated	2026-07-06T21:40:44Z
Pulse	updated
Build dependencies	go
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	flyctl
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

flyctl

nix profile install nixpkgs#flyctl

normalized package name match
Matched by: Flyctl

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/fl/flyctl/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

MacPorts95%

flyctl

sudo port install flyctl

normalized package name match
Matched by: Flyctl

MacPorts ports tree · api.github.com · MacPorts ports tree: devel/flyctl/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

Chocolatey95%

flyctl

choco install flyctl

normalized package name match
Matched by: Flyctl

Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: flyctl from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','flow-launcher'

Scoop95%

main/flyctl

scoop install main/flyctl

normalized package name match
Matched by: Flyctl

Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/flyctl.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

winget95%

Fly-io.flyctl

winget install --id Fly-io.flyctl -e

normalized package name match
Matched by: Flyctl

Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Fly-io.flyctl from https://cdn.winget.microsoft.com/cache/source.msix

Nix92%

fly

nix profile install nixpkgs#fly

installed executable or alias match
Matched by: Fly

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/fl/fly/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

zypper92%

fly 2.0.1-2.6

A Script to Create PNGs

http://martin.gleeson.com/fly/

sudo zypper install fly

License: SUSE-Permissive
Category: Productivity/Graphics/Visualization/Other
Architecture: x86_64
Source Package: fly
2 dependencies
1 provides
installed executable or alias match
Matched by: Fly

openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: fly from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/flyctl.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated agent safety answer
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install flyctl with Homebrew, chocolatey, MacPorts, Nix, scoop, winget, zypper

Agent safety answer

Credential access

Remote mutation

Publish/artifact risk

Recommended control

Agent-use guidance

Additional install commands

macOS

Linux

Windows

Package summary

Project links

Commands and aliases

Project history and usage

Project history

Adoption history

How it is used

Why package nerds care

Timeline

Related projects

Sources

No protected-tool coverage found yet

Install behavior

Recommended review

Configuration and credential file locations

Configuration files

Credential files

Installed executables

Version and freshness

Package metadata

Source database details

Other package-manager records

Internal package links

Topical hubs

Related tools

Same workflow

Agent security guides

Generated from repository data

Combined YAML source

Used sources