Getting Started

Overview

Get productive with Fly in 5 minutes. Install the app, connect your repos, and ship your first release.

Get Up and Running

  1. Download Fly App - Install the Fly App from jfrog.com/fly, or run one of these commands:

    macOS:

    curl -fsSL https://fly.jfrog.ai/download/desktop | bash

    Windows:

    powershell -c "irm https://fly.jfrog.ai/download/desktop | iex"

  2. Sign Up and Create Your Team - Sign up to Fly and pick a team name. This becomes your private registry at <your-team>.jfrog.io.

  3. Start Working with Fly - Ask your coding agent: “Start working with Fly”. Fly connects your repos, configures your CI, and gets you ready to ship.

  4. Generate Your First Release - Approve the PR and run your workflows. Every push now creates a release you can find, share, and deploy.

  5. Deploy and Track Your Runtime - Create an environment, connect your cluster, and deploy: “Deploy the login fix to staging”. Track what’s running from your coding agent.

Download Fly App

The Fly App brings Fly to your machine. Your coding agent, your package managers, and your registry all work together once it’s installed.

Go to jfrog.com/fly and download the Fly App, or copy the curl/PowerShell command and paste it in your coding agent or terminal:

macOS:

curl -fsSL https://fly.jfrog.ai/download/desktop | bash

Windows:

powershell -c "irm https://fly.jfrog.ai/download/desktop | iex"

Grant the necessary permissions when prompted.

Once installed, the app detects your package managers (npm, pip, Docker, Helm, Maven, Gradle, Go, NuGet) and connects your coding agent (Cursor, Copilot, Claude Code, OpenCode) to work with Fly.

Sign Up and Create Your Team

Sign up to Fly and pick a team name. This becomes your private Fly Registry at <your-team>.jfrog.io, where all your releases, packages, and images live. The first user becomes the team Admin with full permissions.

Start Working with Fly

Ask your coding agent:

“Start working with Fly”

Fly asks for access to your GitHub, then opens a pull request that wires your repos into Fly. Review it, merge it, and your CI is live.

What the PR adds to your workflows

  • OIDC permissions let your GitHub Actions authenticate to Fly without storing tokens or secrets, using OIDC:

    permissions:
  contents: read
  id-token: write

  • Fly action auto-configures the package managers on your CI runner (npm, pip, Maven, Docker, Helm, Go, NuGet, Gradle) to pull and push through your Fly Registry:

    - uses: jfrog/fly-action@v1              # Setup Fly package managers

  • Docker and Helm paths point your image and chart references to your private Fly Registry, so pulls and pushes flow through Fly:

    Docker:

    <your-fly-subdomain>.jfrog.io/docker/my-app:tag

    Helm (OCI):

    oci://<your-fly-subdomain>.jfrog.io/helmoci/my-chart

What a configured workflow looks like

npm:

steps:
  - uses: actions/checkout@v6
  - uses: actions/setup-node@v6
    with:
      node-version: '24'
  - uses: jfrog/fly-action@v1              # Setup Fly package managers
  - run: npm install                       # Dependencies from Fly registry
  - run: npm run build
  - run: npm publish                       # Publish to Fly registry

Docker:

steps:
  - uses: actions/checkout@v6
  - uses: jfrog/fly-action@v1              # Setup Fly package managers
  - run: docker build -t ${{ env.FLY_REGISTRY_SUBDOMAIN }}/docker/my-app:${{ github.sha }} .
    # Base images pulled from Fly registry
  - run: docker push ${{ env.FLY_REGISTRY_SUBDOMAIN }}/docker/my-app:${{ github.sha }}
    # Push to Fly registry

Generate Your First Release

Merge the PR, or push any new PR to master. From now on, every PR to master becomes a release in Fly that’s searchable, shareable, and ready to deploy.

Deploy and Track Your Runtime

Now that releases are landing in Fly, connect a runtime environment to deploy them and see what’s running where.

From your coding agent:

“Create a staging environment”

Fly creates the environment and gives you the command to connect it to your cluster. Once connected, every deployment is tracked automatically.

Now you can deploy and track with natural language:

  • “Deploy the login fix to staging”
  • “What’s running in production?”
  • “Is the login fix live in staging?”

You’re all set. Manage your releases, deploy to any environment, and track your runtime right from your coding agent with natural language.

Next Steps