Storage billed at provider rates
Your cloud bills you for bytes at its own price. GitForge bills for the product, not per gigabyte.
Storage
Your bucket, your bytes.
Every commit, pack, and LFS object lands in storage you control — not ours. GitForge is the forge on top; the bytes stay yours, so leaving is just a git clone.
Connectors
15 storage connectors.
Pick the bucket you already pay for. Four consumer clouds connect with one-click OAuth; object stores take your keys; or run the storage yourself.
One-click OAuth
no keys to pasteGoogle Drive
Dropbox
OneDrive
Box
Bring your keys
guided credential setupAWS S3
Cloudflare R2
Google Cloud Storage
Azure Blob
Backblaze B2
DigitalOcean Spaces
Storj
Hetzner Object Storage
Akamai (Linode)
Self-host
your hardware, your rulesMinIO
Any S3-compatible
How it works
Connect once. Every push lands in your bucket.
GitForge's servers are stateless — no repository is pinned to a disk. Objects, packs, and LFS media write straight to the backend you connected, and stay readable to you forever.
Storage settings
EncryptedFrom bucket to forge
Connect a backend
Push like alwaysobjects/ · lfs/
Leave anytimegit clone
Backed by your storage leave anytime
Cost
Storage prices, not hosting markup.
You pay your cloud for bytes and GitForge for the forge. The two never multiply each other.
Seats never multiply storage
Adding a collaborator never re-bills the repository — storage cost is independent of team size.
Zero egress on R2
Cloudflare R2 charges nothing to move data out, so clones and migrations are free at the storage layer.
Keep exploring
Enterprise Customer-managed keys and governance over the same buckets.Features The full platform running on top of your storage.Factory AI agents whose output lands in your bucket too.Pricing Free to start; storage is never billed per seat.GitForge vs GitHub Same workflow — minus somebody else's storage bill.
Get started
Connect the bucket you already pay for.
Free to start — push your first commit to your own storage today.