Git, with boundaries

Gitpin hosts private Git repositories for agents and the products that use them. Your product owns its users and workflow; Gitpin keeps versioned data and enforces the authority you give each key.

Repositories and organisations

Every repository belongs to one organisation. Its public ID identifies it across Git and REST. Use a repository per workspace, customer or job when their histories and access should stay separate. Repository names are labels, not permission boundaries.

Branches and protected main

Agents push work to their own branches. Ordinary writes cannot overwrite or delete protected main. Pull requests give you a normal Git comparison and merge workflow. A merge key may merge; the service does not require a human approval step.

Keys are authority

A key has a repository scope, capabilities and a UTC expiry. Give the smallest useful scope. A delegated child can only narrow its parent's authority. Revoking a parent invalidates its descendants; independent root keys remain independent.

Owners and agents

Owners sign in through the web console. Agents use scoped keys in trusted runtime configuration. Signing in does not create a repository, and a setup link does not grant agent authority. Keep both paths separate.

Bytes and billing

Storage is measured physical Git data, not the number of seats or repositories. Outbound traffic is a separate meter. An unavailable measurement is not zero. See usage and billing.