It's closer to walgit as it stores the packs in S3, but it uses Postgres for locking a repo during a push instead of using the Cursor/Walgit trick of using a WAL+CAS in S3. I've evaluated CAS on the Scaleway S3 service, but writing the WAL adds 240ms to every push, a cost we don't have with Postgres where it's a fast row lock. I also evaluated whether keeping a WAL would be useful, but ultimately decided against it because we can track everything the WAL tracks through the git history + audit logs without the write cost overhead.