eyebluecn/tank

《蓝眼云盘》(Eyeblue Cloud Storage)

View on GitHub ↗Jump to charts ↓

eyebluecn/tank has 3k+ stars and 500+ forks on GitHub, is written in Go, and was last pushed on Feb 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on December 23rd, 2017
Open Issues & Pull Requests: 39 (+0)
GitHub issues: Enabled
Number of forks: 548
Total Stargazers: 3,237 (+0)
Total Subscribers: 59 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.3 days
Mean response time: 128.7 days
90th percentile: 322.5 days
Tracked items: 10

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 27
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 490 days
Stale 30+ days: 26
Stale 90+ days: 26

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Tank is a self-hosted cloud storage system written in Go that enables users to deploy their own file storage and sharing infrastructure.

The project addresses the need for private, self-controlled file storage by providing a complete cloud storage solution that can be deployed on personal servers or infrastructure. It handles file upload, storage, organization, and sharing capabilities, allowing users to maintain full control over their data rather than relying on third-party cloud providers. The system is built in Go, which provides efficient performance and straightforward deployment characteristics.

Tank suits organizations and individuals who prioritize data privacy and want to avoid dependency on commercial cloud storage services. It works well for teams that need internal file sharing, document management, or backup capabilities within their own infrastructure. The project is particularly relevant for users operating in environments where data residency requirements or security policies mandate on-premises solutions. Those evaluating adoption should expect to manage their own server infrastructure and maintenance, as this is a self-hosted offering rather than a managed service.

The project maintains active development with regular updates to its codebase. Documentation is provided through a dedicated documentation site, indicating ongoing effort to support users. The repository shows consistent engagement with improvements and maintenance of the core storage functionality.