Github has suffered reliability issues as of late, due to 10x commit volume from vibe coding, leading many seeking other providers or self hosting their own git repositories.

Instead of using a third party provider, you can use your own cloud storage, such as Google Drive, to store your private git repositories. This approach works with Google Drive, MS One Drive, iCloud, DropBox, Backblaze or any cloud storage that has a desktop client. No additional servers are needed, and syncing uses the exact same git commands you are familiar with : git push, pull, fetch , gc etc.

As systems grow, the “one repo per microservice” pattern can lead to significant overhead: dependency hell, fragmented CI/CD, and difficulty in cross-service refactoring. Migrating to a monorepo often becomes the logical next step for many engineering teams.

Monorepo Migration

The biggest technical challenge during this migration is preserving the commit history of each individual service. You don’t want to just copy files; you want to bring the years of context, bug fixes, and development history with them.