# What we learned shipping a git platform

> Notes from a small team building hosting, review, CI, and automation at once: the boundaries we drew and the ones we had to redraw.

Published: 2026-06-04
Author: Trylle
Tags: Company, Engineering culture

Building four products at the same time only works if you are ruthless about which one owns each fact.

## One owner per fact

Repositories, branches, commits, and reviews have a single authoritative source. Everything else reads through it. The moment we allowed a second copy "just for the dashboard", we started shipping bugs where two screens disagreed about the same pull request.

## Caches are not truth

Derived values live in a cache with an explicit expiry and a background refresh. They never become the thing a merge decision is made from. That rule cost us some latency and saved us an entire class of stale-state incident.

## Redraw early

The boundaries we set in the first month were mostly right. The two we got wrong were cheap to move then and would have been very expensive to move now.

---

Canonical: https://blog.trylle.com/what-we-learned-shipping-a-git-platform