Directory DevOps & Platform EngineeringArtifact & Package ManagementDragonfly

Dragonfly

Open Source

About Dragonfly

Dragonfly is a data distribution system. It uses P2P technology to use idle bandwidth of a Peer to improve download speed. It provides non-intrusive support for multiple container runtimes, download tools, and AI infrastructure. Peer configuration settings such as load limit, concurrent limit, and traffic limit can be configured. It ensures downloaded files are consistent even if the user does not check for consistency. It isolates exceptions based on Service level, Peer level and Task level to improve download stability.

Products

Dragonfly 1.0: Version open sourced and used in production environments by many companies.
Dragonfly 2.0: Version released after architectural optimization and code refactoring.

Used for

Improving download speed using idle Peer bandwidth
Integrating with AI infrastructure, container runtimes, container registry, and download tools
Configuring load limit, concurrent limit, and traffic limit for Peers
Isolating exceptions at Service level, Peer level and Task level

From Dragonfly's own website, read 2026-10-23. How we build listings.

How to evaluate Artifact & Package Management

This is how the CIOPages Research Team evaluates this category. It is not an assessment of Dragonfly. It comes from our Container Registry & Artifact Management buyer guide.

25%

Supply-Chain Security & Provenance

Built-in vulnerability scanning (and whether it scans the binary or just the manifest), Cosign/Notation signing with content-trust enforcement, SBOM generation and storage (CycloneDX / SPDX), SLSA-style build provenance and attestation, and proactive quarantine of malicious or typosquatted dependencies before they enter

20%

Artifact & Format Breadth

Container/OCI plus the language ecosystems you actually use (npm, Maven/Gradle, PyPI, NuGet, RubyGems, Go, Helm, Debian/RPM); OCI-artifact support for non-image content; remote/proxy and virtual (aggregating) repositories; and whether one platform covers everything or you stitch several together

15%

Access Control, Multi-Tenancy & Governance

SSO/SAML/OIDC and SCIM, fine-grained and project-scoped RBAC, immutable tags and retention/cleanup policies, environment-promotion gates (dev→staging→prod), tamper-evident audit logging, and compliance posture (SOC 2 Type II, ISO 27001, FedRAMP where relevant)

15%

Distribution, Performance & Availability

Pull-through caching of upstream registries, geo-replication / edge distribution to your runtime regions, deduplication and storage efficiency, high availability and DR, and pull latency and throughput under CI burst and large-image load

15%

CI/CD & Platform Integration

Native hooks into your CI (GitHub Actions, GitLab, Jenkins, Argo), Kubernetes admission-control and OIDC-based keyless auth, webhooks/events, a complete REST API and Terraform provider for IaC, and cloud IAM integration if you live in one provider

10%

Operations & Cost Model

Self-managed vs. SaaS effort, upgrade and HA burden for self-hosted options, and how the meter works — per-user, storage, egress/data-transfer, or per-scan — because the unit of billing, not the headline rate, decides what you pay as pulls and image counts grow

Other Artifact & Package Management Vendors

View all

Alibaba Cloud Container Registry (ACR)

Amazon Elastic Container Registry (ECR)

Artifact Hub

Azure Registry

Cloudsmith

Google Container Registry

CIOPages put this listing together from public sources. It’s information, not an endorsement. How we build listings. Work here? Claim this listing or .