A Git host for teams that want an alternative.
PearlGit is operated by PearlFibers — a small engineering team building a stack of products for serious development teams.
What we believe.
A Git host shouldnt be a long-term hostage situation. We built PearlGit because every popular alternative leaves teams choosing between vendor lock-in, a contract bill that keeps growing, or rolling their own infrastructure they dont want to operate.
PearlGit sits between those options: the same binary runs in our cloud and in your VPC. Plain Git is the only protocol you ever depend on. If we stop earning your business, your exit is a clone and a DNS change.
Who builds PearlGit.
PearlGit is one product in a stack we operate at PearlFibers:
- Loop — collaboration platform and SSO identity service.
- Pearl IDE — AI-native desktop and browser code editor.
- Peak AI — AI chat product.
- PearlGit — what youre looking at now.
One sign-in across all of them via Loop SSO. We use these tools to build them, so the rough edges hit us first.
Were a small engineering team, not venture-backed, not racing to a hype-cycle exit. We build software for teams that want to keep using it in five years.
How we work.
- Ship weekly. The changelog is the ground truth.
- Sales is engineering-adjacent. Pricing conversations happen with people who can answer technical questions in the same call.
- Support is the team. Your email lands in the engineering queue — same one we work from.
- No dark patterns. No "free tier" with surprise asterisks, no upsell wall on basic security features, no "we noticed youre cancelling" friction.
- Plain Git underneath. The exit door is the front door. If we stop earning your business, you can leave.
Contact.
- General: hello@pearlfibers.com — same-day reply on business days.
- Sales: sales@pearlfibers.com — for pricing, plan changes, migrations.
- Security: security@pearlfibers.com — for vulnerability reports.
- Press: press@pearlfibers.com
- Legal: legal@pearlfibers.com
The fastest way to evaluate PearlGit is to use it.
Talk to sales for terms, or just migrate a single repo to try the workflow on real code.