OSS Tanbou

flyctl — manage Fly.io applications, Machines, and networking from the terminal

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
1,704
Primary language
Go
License
Apache-2.0
Repository last updated
Sep 19, 2026

Overview

flyctl is the official command-line interface for Fly.io applications, Machines, deployments, secrets, networking, and related resources. After authentication, it can inspect account and app state and drive deployment workflows around `fly.toml`.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Inspect account, applications, and status from the CLI

After login, commands can list applications and inspect status and configuration for a selected app.

Sources: [2]

Expand into deployments, Machines, secrets, and networking

The CLI covers application lifecycle operations plus Fly Machines, secrets, and network-related resource management.

Sources: [1][3]

For scripting Fly.io deployment workflows locally and in CI

It fits teams that want infrastructure operations represented as project configuration and repeatable commands rather than only web-console steps.

Sources: [2]

Make the target app explicit before mutating production resources

Commands may infer an application from the current fly.toml. Multi-environment workflows should explicitly select the intended app before deployment or resource changes.

Sources: [2]

Official sources

  1. [1]superfly/flyctl repository(2026-09-21)
  2. [2]flyctl README(2026-09-21)
  3. [3]Fly.io documentation(2026-09-21)
  4. [4]flyctl v0.4.104 release(2026-09-21)
  5. [5]flyctl Apache-2.0 license(2026-09-21)
Supplemental curator note

The latest GitHub release is 0.4.104. The README notes that `flyctl` and `fly` command names coexist during a transition. Many commands infer the target application from `fly.toml` in the current directory, so multi-app workflows should make the target explicit.

Try it in 3 steps

  1. 1

    Install flyctl

    Use the package-manager path documented in the README; Homebrew works on macOS, Linux, and WSL.

    brew install flyctl
  2. 2

    Authenticate with Fly.io

    Complete browser authentication so the CLI can access the account.

    fly auth login
  3. 3

    Inspect apps and status

    Start with read-only inspection and explicitly select the application before making production changes.

    fly apps list && fly status -a <app-name>
Check the official README

Growth

Growth trends · Last 30 days

1,704 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
71
Open PRs
50

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • flyio-tools
Stars
1,704
Forks
311
Watchers
23
Open issues
170
Contributors
223
Primary language
Go
License
Apache-2.0
Repository last updated
Sep 19, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.