Hoq Repos
Private git hosting for your organization — encrypted at rest, backed up off-site every night, with code review that has teeth and access you can scope to a person, a team or an AI agent.
Git hosting, private by default
Repositories live at git.hoq.app and speak plain git over HTTPS and SSH — clone, push, everything your tools already do. Every owner's repositories are stored encrypted under a key of their own, and each night every repository's encrypted data is copied to a second storage provider, with deleted data kept for 60 days.
- SSH keys and HTTPS clone keys on your account, listed and revocable.
- Deploy keys that belong to a repository rather than a person — read-only or read and push.
- Every push is recorded with the commits, files and checks it brought in, and branches and tags can be restored to how they were at any push, with a preview first.
- Mirrors: follow another repository, or copy every new push to one elsewhere.
- Signed webhooks to your own URLs when something happens, retrying for about eight hours.
Reading and reviewing code
The browser shows files, folders, READMEs, raw files and blame, with the last commit on each file. Code search takes regex and case options; commits and diffs read side by side or unified; any two branches, tags, commits or pushes can be compared and shared as a link. Commits signed by a known person are marked — and so are unknown keys and bad signatures.
Changes and review
- Open a change from a branch and merge by merge, squash or fast-forward, with fix-up commands for conflicts.
- Line-level comments with replies and resolving; each push to a change is a revision you can compare, and files you have viewed are marked.
- Approvals required before merge when the repository turns the rule on; checks can block a merge until tests pass.
- Protected branches stop direct pushes so work goes through a change.
- An inbox collects the changes that need you, with approve and reply in place.
People, teams and agents
Repositories sit under a person or an organization, in groups, with read or write access given to people or teams by email. Deleted repositories wait in trash to restore, or go for good after typing the name. Storage is billed daily — to the organization for its repositories, to you for yours.
AI agents get first-class treatment: a key marked as an agent's, with its own name, limited to chosen repositories or whole organizations, able to create repositories there if allowed, and paused at a button. Agents can list, read, search and compare repositories through an MCP endpoint without cloning, and an agent's work on protected branches goes through a change like anyone else's.
Watching the work
- What was pushed since your last visit, with a count on the repository list.
- Repository stats: lines of code by language, commits, contributors, age, size, largest files.
- A command center — a dense, live, terminal-style view of every repository and its activity.
- Work and Story: how much landed in a period and who did it, and the same commits told as readable entries grouped by day, with a short written summary on demand.
Next step
Tell us how your team works — where your code lives today and what you need from hosting. We'll take it from there.