GitGres, an open‑source project by Caleb Win, positions itself as a self‑hosted GitHub alternative that stores every Git object, pull‑request metadata and team information inside a PostgreSQL database. By moving the entire collaboration surface from disk to rows, it gives teams granular control over cost, uptime and data locality that the public service can’t match overall.

The design trades traditional GitHub trade‑offs: cost for uptime, latency for price, and strict consistency for throughput. Users can attach PostgreSQL tiered storage to lower expenses, pick a cache extension to squeeze latency, and run the server locally or co‑located with CI agents for tunable consistency. Because nothing lives on disk, backup and replication follow standard Postgres patterns in production.

Getting GitGres running requires a Rust toolchain, a reachable Postgres instance and a few environment variables. After `cargo build --release`, `gitgres init` applies an idempotent schema, then `gitgres serve` launches the HTTP API; the first call generates an admin token tied to a demo user. The CLI mirrors GitHub’s `gh` commands, though features like search, actions and webhooks remain absent.