Your bucket, your bytes.
15 storage connectors, one-click OAuth for four of them. Self-host S3, R2, or MinIO if you'd rather run it yourself. GitForge never becomes the single copy of your history.
See the connectorsGitForge hosts your git repos in storage you already own.
Own your bytes. Leave anytime — git clone is the whole migration.
No export request, no migration tool, no waiting on support. Your objects are already sitting in your bucket.
Your bucket, your bytes
Connect your storage in one click.
Pick Drive, Dropbox, or OneDrive for one-click OAuth, or hand GitForge credentials for S3, R2, GCS, or Azure Blob. Every commit, blob, and pack file lands in that account, not ours.
See how storage worksYou pay your cloud's storage price, not a per-seat hosting fee — and R2 storage moves data out for free.
Why GitForge
What you're actually getting.
No lock-in, storage priced like storage instead of like seats, a full forge built on top, and AI agents that work where your code already lives.
Storage prices, not hosting markup.
You're billed for GitForge the product, and your cloud bills you for storage at its own rate — no per-seat tax on top of every gigabyte, no egress bill if you're on R2.
Compare to GitHubStill a full forge.
Pull requests, issues, CI/CD pipelines, Git LFS, RBAC down to the path, SSO and SCIM — the whole platform runs on top of the storage you connected, not instead of it.
See what's includedAI agents, sandboxed, in your repos.
Spin up a hardened container that clones, branches, and opens pull requests against your repos. Each session runs isolated, and every object it writes still lands in your bucket.
Read about FactoryGet started
Push your first repo in minutes.
Connect the bucket you already pay for and push your first commit today.