gith.

Design exploration / 01

Ten reasons to run
your own Git host.

Each direction tests a different market position—not merely another skin. Open one to judge the full composition; the previous design remains preserved as the baseline.

BASE

Current direction

Editorial infrastructure · warm paper · system diagram

↗
01

Own the host

Sovereignty angle · your machine, repositories, and rules

↗
02

Almost zero-ops

Simplicity angle · one binary and the tools already installed

↗
03

The admin panel is a commit

Git-native angle · change access the way you change code

↗
04

The narrow gate

Security angle · no shell, vague roles, or unaudited action

↗
05

Private on first push

Ease angle · create a repository without a dashboard

↗
06

When in doubt, stop

Reliability angle · failure leaves the last good state intact

↗
07

Every yes has a reason

Audit angle · decisions tied to rules and request IDs

↗
08

Principals for machines

Automation angle · tightly scoped access for CI and AI

↗
09

Do not reinvent Git

Trust angle · OpenSSH, Apache, and system Git

↗
10

Small enough to understand

Independence angle · the whole host fits in your head

↗
Prototype gallery · pick one direction or combine the strongest parts.