dragonflyoss/dragonfly

Delivers efficient, stable, and secure data distribution and acceleration powered by P2P technology, with an optional content‑addressable filesystem that...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 21 minutes ago
Added to GitGenius on September 20th, 2026
Created on November 4th, 2020
Open Issues & Pull Requests: 25 (+0)
GitHub issues: Enabled
Number of forks: 427
Total Stargazers: 3,334 (+0)
Total Subscribers: 36 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 235 days
Stale 30+ days: 14
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (113)
  • bug (112)
  • help wanted (49)
  • good first issue (42)
  • client (14)
  • on-hold (14)
  • question (8)
  • documentation (7)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Dragonfly is a P2P-powered data distribution and acceleration system designed for cloud-native environments that optionally includes a content-addressable filesystem to speed up OCI container image launches.

The tool addresses the challenge of efficiently distributing large files and container images across cloud infrastructure at scale. It works by leveraging peer-to-peer technology to distribute data, reducing reliance on centralized registries and improving delivery speed and stability. The optional content-addressable filesystem component accelerates container startup by enabling more efficient image layer access patterns.

Dragonfly suits organizations operating large-scale cloud-native deployments where container image distribution, artifact delivery, or model distribution represents a bottleneck. It is particularly relevant for scenarios involving frequent container launches, large AI/ML model distribution, or environments with many nodes pulling the same artifacts. The project targets cloud-native architectures and integrates with OCI standards, making it applicable to Kubernetes clusters and container orchestration platforms.

The project maintains active community engagement through multiple channels including a dedicated Slack workspace, discussion forums, and developer mailing lists. Development activity includes regular security practices, with third-party security audits conducted and vulnerability reporting processes documented. The team publishes software bills of materials alongside releases and maintains a public roadmap in a separate community repository. Contribution guidelines and a code of conduct are established and enforced across the community.