Getting Started

Get Up and Running

  1. Download Fly App - Install the app and sign up to get started.
  2. Create Your Team - Pick a team name. This becomes your private registry at <your-team>.jfrog.io.
  3. Start Working with Fly - Open your IDE and ask: “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 with full traceability.
  5. Deploy and Track Your Runtime - Create an environment, connect it to your K8s namespace, and deploy: “Deploy the login fix to staging”. Track what’s running from your IDE or Fly Chat.

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

Download Fly App

The Fly App is your local bridge to Fly. It connects your IDE, your package managers, and your registry.

  1. Request beta access at jfrog.com/fly. Once approved, you’ll receive an email invitation.
  2. Download the Fly App from Fly Web: click the Desktop icon, then Connect.
  3. Run the installer and grant the necessary permissions.

Supported platforms: macOS and Windows.

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

Create Your Team

Sign up with GitHub, Google, or Email + Password, then 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.

Note: This is not a web interface. Access Fly Web at fly.jfrog.ai.

Start Working with Fly

Open your IDE and ask your coding agent:

“Start working with Fly”

That’s it. Review the PR, merge, and you’re done.

What Fly does:

Fly opens a GitHub authorization flow, connects your repositories, scans your workflows, and creates a pull request with the CI configuration. The PR adds two things to your workflows:

OIDC permissions for secure, token-free authentication:

permissions:
  contents: read
  id-token: write

Fly action to configure your package managers on the CI runner:

- name: JFrog Fly - Configure all your package managers to work with Fly registry
  uses: jfrog/fly-action@v1
  with:
    url: https://<your-fly-subdomain>.jfrog.io

For Docker, Fly also sets your image path to point to Fly Registry: <your-fly-subdomain>.jfrog.io/docker/my-app:tag

Deploy and Track Your Runtime

Once your releases are flowing, connect your runtime environments to complete the picture.

From your IDE:

“Create a staging environment”

Fly creates the environment and helps you connect it by generating a token and providing the kubectl command to apply the image pull secret to your K8s namespace. Once connected, every image pull is tracked.

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?”

Deploy and Track Your Runtime

Once your releases are flowing, connect your runtime environments to complete the picture.

From your IDE:

“Create a staging environment”

Fly creates the environment and helps you connect it by generating a token and providing the kubectl command to apply the image pull secret to your K8s namespace. Once connected, every image pull is tracked.

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?”

What You Get

Your IDE is where you work with Fly. Through Fly MCP, your coding agent can manage releases, configure CI, deploy, and query your runtime, all with natural language.

Fly App is your local bridge. It auto-configures your package managers and IDE, and keeps your connection to Fly running in the background.

Fly Web is your team’s hub for releases, artifacts, environments, and team management. Access it at fly.jfrog.ai.

Fly Registry is where your packages and images live, at <your-team>.jfrog.io. Every package manager and CI workflow points here.

Next Steps

Developer Workflow → - Manage releases, deploy, and track your runtime

Fly Web → - Explore your releases, environments, and team settings

FAQ → - Common questions and answers