Self-hosted git, without the ceremony
Version control that stays calm.
Pebble hosts your repositories on infrastructure you own. A content-addressed object store, a small Rust CLI, and a web view that never gets in the way.
- [LICENCE] licensed
- Self-host or use ours
- sha256 content addressing
Everything a repository needs. Nothing it doesn't.
Five pieces, each doing one job well.
Content-addressed storage
Every object is <type>\0<payload>, addressed by the sha256 of those bytes. The server re-hashes each upload before it's stored — the same integrity check the CLI runs locally.
Proposals, not pull requests
Propose a change, review the three-way merge, land it. Merge conflicts use the markers you already know.
A CLI that reads like prose
p push, p log, p tree. One verb, one job.
Web views that don't edit
Browse history, trees, and diffs in the browser. Changes happen through the CLI or a proposal — never a form.
Your nodes, your regions
Enrol a machine, give it a region, and it reports in. Storage limits, job concurrency, and maintenance mode are per node.
Runs where you need it to.
Three regions today. More as we grow — and you can always run your own.
Pebble is self-hostable first. Every node you enrol reports its region, health, and resource use, so you can see your whole fleet in one place.
We also run managed regions for teams who'd rather not. Both use the same node protocol — nothing about the managed version is special.
- Live
- Planned
- Your nodes
| City | Country | Region | Status | Planned for |
|---|---|---|---|---|
| Amsterdam | NL | eu-west | Live | Not applicable |
| Frankfurt | DE | eu-central | Live | Not applicable |
| Ashburn | US | us-east | Live | Not applicable |
| Portland | US | us-west | Planned | 2026 Q4 |
| Mumbai | IN | ap-south | Planned | 2027 Q1 |
| Singapore | SG | ap-southeast | Planned | 2027 Q1 |
| São Paulo | BR | sa-east | Planned | 2027 Q2 |
Made for the terminal you already live in.
No new mental model. No web form to push code through.
$ p clone pebble/nest → 1,284 objects, 12.4 MB$ p log --limit 3 a3f9c21 Add fast-forward check to ref advance 7b1e884 Port change_blocks to the web diff view 0d4c5f2 Bump heartbeat interval default to 30s$ p push → refs/heads/main 0d4c5f2 → a3f9c21 (fast-forward)Fast-forward only, by default.
A push that isn't a fast-forward is refused, not force-merged. You decide what to do next.
The format is documented.
Objects are files. Refs are files containing a sha. You can read your repository with cat.
No lock-in by construction.
If Pebble disappeared tomorrow, your object store is still on your disk and still readable.
Ready for the parts nobody enjoys.
Data residency, audit trails, and access control — because you'll be asked.
Data residency
Run every node in one jurisdiction, or air-gap entirely. Nothing phones home.
Append-only audit trail
Every privileged action is recorded with actor, target, and time. Admins can filter by category and export.
Role-based access
Repository visibility, per-token scopes, and required approvals on protected branches.
Single sign-on
OpenID Connect via your existing provider — GitHub, Google, GitLab, Atlassian, and six more.
Judge it by the source, not the testimonials.
We're pre-launch. Here's what you can check today instead.
Read the object format.
The storage layer is documented and the CLI is its reference implementation.
Source link coming soon.
Read the merge engine.
Three-way merge, merge-base detection, and the conflict markers — all in the open.
Source link coming soon.
Watch it get built.
Commits, proposals, and design notes as they happen.
Source link coming soon.
Questions you're probably about to ask.
Not wire-compatible. Pebble uses its own content-addressed object format — similar ideas, different bytes — so git push won't talk to it. Import tooling is planned; if that's a blocker for you, say so on the waitlist form and we'll prioritise accordingly.
Get an invite.
Name and email. Nothing else, and no marketing.