Artifacts
Overview
An artifact is any package, library, or container image that your team builds or depends on – npm packages, Docker images, Helm charts, Python wheels, Maven JARs, Go modules, and more. In Fly, artifacts are the building blocks of your releases.
Every artifact your team publishes ends up in Fly Registry, where it’s stored securely, linked back to the code that produced it, and available to your entire team. Fly also caches public dependencies so your builds are faster and more reliable.
- Uploaded Artifacts – Packages you or your team have published (from CI/CD or local development)
- Public Dependencies – Packages from public registries (npm, PyPI, Maven Central, DockerHub, etc.) that have been cached in Fly
All artifacts are stored in your private Fly Registry at <your-fly-subdomain>.jfrog.io.
How It Works
Lifecycle
Upload – Artifacts are published in two ways:
- CI Workflows – GitHub Actions workflows automatically upload artifacts when the Fly action is configured. Learn more →
- Local Development – Upload from your workstation using standard package manager commands. The Fly App handles authentication automatically. Learn more →
Storage – All artifacts are stored in your Fly Registry with secure, encrypted storage.
Download – Artifacts can be downloaded by team members, CI/CD workflows (via OIDC), and external systems (via tokens).
Public Dependencies are automatically cached when first requested from public registries.
Artifact Identity
Each artifact has:
- Name – The package name
- Type – Package manager type (npm, docker, helm, pip, etc.)
- Version – Version identifier
- Git Repository – The repository that produced it (if available)
Artifacts with the same name are grouped together, with the latest version shown by default.
From Your Coding Agent
Your coding agent can publish, find, and manage artifacts using natural language. The Fly App handles authentication and registry routing in the background – no manual configuration needed.
Publish Artifacts
“Publish this npm package to Fly”
“Push this Docker image”
Your coding agent handles authentication and routing. Learn more →
Find Artifacts
“Find my latest artifact”
“Show me all npm packages uploaded this week”
Fly searches across your artifacts to find what you need.
In Fly Web
Fly Web lets you browse all artifacts across your registry, drill into version history, and manage artifacts visually. You can view artifacts across your entire team or scoped to a specific Git repository.
Artifact Views
All Artifacts Tab – Every artifact in your Fly Registry, including those without Git repository association.
Git Repository View – Navigate to a specific repository to see its associated artifacts.
List View
| Column | Description |
|---|---|
| Name | Artifact package name |
| Type | Package manager type |
| Latest Version | Most recent version number |
| Last Updated | When the latest version was uploaded |
| Git Repository | Repository that produced the artifact |
Click any artifact to see its detail view with specific version details and complete version history.
Actions
- Download – Use standard package manager commands or ask your coding agent
- Delete Versions – Admins can select and permanently delete artifact versions from the detail page
Next Steps
- Package Types → - Registry configuration for each package manager
- Releases → - Releases that produce artifacts
- Developer Workflow → - Publish and manage artifacts locally