Where to Use Fly

Overview

Wherever you work, Fly is with you. It’s in your coding agent, your CI, your terminal, Slack, and your browser. Use whichever interfaces boost your productivity: one, all, or a mix.

Interfaces

  • Fly App — The bridge between your local tools and Fly. Installs once, runs in your menu bar (macOS) or system tray (Windows). Detects your package managers and coding agents and handles authentication automatically. Install it first; the others depend on it.
  • Coding agent — Where you develop and ship. Fly integrates with your IDE through Fly MCP and skills. Ask anything: “release a new version”, “show me the release that fixed authentication”, “what’s running in production?”
  • Fly Web — Your team’s central hub at fly.jfrog.ai. Browse releases, compare environments, view artifacts, manage repositories and team access. Fly Chat is built into every page.
  • CI — Where your release pipeline runs. Configure your workflows once with your coding agent. Every push that produces an artifact becomes a tracked release, automatically.
  • Terminal — For direct artifact work. Upload or download from your shell: npm publish, docker push, helm upload. They all land in your Fly Registry; the Fly App handles auth in the background.
  • Slack — Where notifications arrive. Get pinged when security fixes hit prod, deploys fail, or something you watched happens. You can also ask Fly quick questions in any channel.

Next steps