-
Interest in using object storage for Git – Many commenters wish Git repositories could rely purely on object storage rather than a traditional filesystem.
“I saw some git‑on‑durable‑objects projects but I’d so much prefer a straight object storage option.” – mmastrac
“It’s kinda wild to me that this hasn’t been done. Would be so much nicer if gitlab/forgejo/gitea/… supported object storage for everything.” – mgrandl -
Proposals for technical improvements to Git – Suggestions include Merkle Patricia trees, better delta object storage, and BitTorrent‑like distribution for deduplication.
“Next: replace whole-file hashes with a Merkle Patricia tree hash and enable BitTorrent‑like distribution protocols on top, not to mention the deduplication advantages!” – jiggawatts
“Finally delta objects should be stored as their own object in the packfile… so that you don’t have to read the object and its deltas to read the object in the first place.” – hanwenn -
Skepticism about novelty or possible spam – Some users note the frequent reposting of similar projects and question whether it’s a marketing push.
“4th submission in 3 days. Is this a marketing spam campaign?” – 0bytes
You can run Git on object storage if you re-make packfiles
📝 Discussion Summary (Click to expand)
🚀 Project Ideas
Generating project ideas…
Git-Object-Storage Adapter for Self‑Hosted Git Servers
Summary
- A pluggable storage layer for Gitea, GitLab, or Forgejo that writes all Git objects, refs, and packs directly to S3‑compatible object storage while maintaining a local read‑through cache.
- Core value: eliminates the need for a POSIX filesystem on the Git server, enabling truly stateless, horizontally scalable Git hosting.
Details
| Key | Value |
|---|---|
| Target Audience | Self‑hosted Git administrators (small teams to enterprises) who want to run Git on Kubernetes, serverless, or edge environments without managing disks. |
| Core Feature | Transparent object‑storage backend with configurable cache TTL, atomic multipart uploads for packfiles, and distributed lock service (e.g., DynamoDB or Consul) to prevent concurrent pushes. |
| Tech Stack | Go (adapter), gRPC for cache coordination, AWS SDK / MinIO client, Prometheus metrics, Docker/Kubernetes Helm chart. |
| Difficulty | Medium |
| Monetization | Hobby |
Notes
- HN users complained: “I’d so much prefer a straight object storage option.” and “Would be so much nicer if gitlab/forgejo/gitea… supported object storage for everything.” This adapter directly satisfies those wishes.
- Enables discussion about stateless Git ops, benchmarking against traditional NFS/SSD backends, and opens possibilities for edge‑deployed Git runners.
ObjectGit: Fully Managed Git‑as‑Object‑Storage Service
Summary
- A SaaS platform where each Git repository is backed by its own isolated object storage bucket (S3‑compatible) and accessed via standard Git over HTTP/SSH, with zero server‑side filesystem.
- Core value: provides Git hosting that scales automatically with storage usage, removes disk‑size limits, and offers instant snapshotting via object‑storage versioning.
Details
| Key | Value |
|---|---|
| Target Audience | Developers and DevOps teams looking for low‑maintenance Git hosting (e.g., startups, open‑source projects) who prefer pay‑as‑you‑go storage over fixed‑size VM disks. |
| Core Feature | API‑driven provisioning of repos; push/pull handled by a thin stateless gateway that translates Git protocol calls to object‑storage GET/PUT/DELETE operations, with server‑side packfile generation on demand. |
| Tech Stack | Node.js/TypeScript gateway, AWS S3 API (or compatible), Redis for pub/sub locking, Terraform provider for repo creation, CI/CD pipelines for updates. |
| Difficulty | High |
| Monetization | Revenue-ready: tiered pricing based on stored GB and monthly Git bandwidth (e.g., $0.023/GB storage + $0.09/GB transfer). |
Notes
- Commenters wanted “GitLab/Forgejo/Gitea… supported object storage for everything.” ObjectGit offers exactly that as a managed service, removing the operational burden.
- Sparks conversation about cost models for Git‑centric workloads, integration with CI systems, and comparison to existing GitHub/GitLab pricing models.
git‑remote‑obj: Universal Git Remote Helper for Object Storage
Summary
- A git remote helper (
git remote obj) that lets any Git client treat an S3‑compatible bucket (or Cloudflare R2, etc.) as a remote repository, handling packfile negotiation, object upload/download, and locking automatically. - Core value: enables developers to use familiar Git workflows directly against pure object storage without setting up a traditional Git server.
Details
| Key | Value |
|---|---|
| Target Audience | Individual developers, open‑source maintainers, and small teams who want to host personal or project repos on cheap object storage (e.g., free tier S3, R2) while retaining full Git compatibility. |
| Core Feature | Implements git push, git fetch, git clone, and git ls-remote over object storage, with automatic packfile creation on push and incremental fetch; uses lightweight lock objects to avoid race conditions. |
| Tech Stack | Rust (for speed and safety), async Tokio, AWS SDK, optional SQLite for local metadata cache, distributed lock via DynamoDB or Consul. |
| Difficulty | Medium |
| Monetization | Hobby |
Notes
- HN sentiment: “I saw some git‑on‑durable‑objects projects but I’d so much prefer a straight object storage option.” This helper provides that straight option, usable today with any bucket.
- Encourages discussion about decentralized Git hosting, interoperability with GUI tools (GitHub Desktop, VS Code), and potential for integrating with static‑site generators or data‑lake workflows.