Chapter II · The Arsenal
Bring your own bucket — 15 storage connectors as collectible loot, one-click OAuth for four.
Read this chapterChapter I · The Call
Git hosting on your own storage.
Your git objects live in the bucket, Drive, or R2 endpoint you already own — not a filesystem GitForge controls. Stateless. Portable. Yours.
15+ connectorsone-click oauthzero egress on r2
Bring your own bucket
Connect your storage in one click.
Keep every git object in infrastructure you already control. Choose an OAuth provider or bring credentials for your cloud, then GitForge handles the rest.
See how storage worksStorage settings
EncryptedConnect your storage
Google DriveOne-click OAuth
DropboxOne-click OAuth
OneDriveOne-click OAuth
BoxOne-click OAuth
AWS S3
Cloudflare R2
Google Cloud Storage
Azure Blob
Backed by Google Drive 0 egress
The quest
Your repo's quest, chapter by chapter.
From the first connected bucket to the full platform at scale, your code stays portable at every step.
Chapter III · Old Foes, Slain
Vendor lock-in, egress bills, per-seat pricing — the enemies other hosts lose to, defeated.
Read this chapterChapter IV · The Dragon
The full platform at scale — SSH/HTTP, LFS, PRs, issues, CI, RBAC/SSO — on your own storage.
Read this chapterChapter V · The Forge
Forge sandboxed AI coding agents that work in your repos — each session runs in its own hardened container.
Read this chapterBegin the quest
Push your first repo in minutes.
Connect the storage you already own and keep your code portable from the very first commit.