Frequently asked questions

No. Developers keep working in GitHub or GitLab as usual. GitHood syncs everything automatically. The only optional input is a short patch note in their PR description. They can check GitHood for visibility into what's happening across the team, but nothing is required.

Through personal access tokens for GitHub and GitLab. We read repository metadata and pull request activity. We never read or store your source code.

Yes. GitHub and GitLab both work. You can mix repositories from different organizations and providers in a single workspace.

Whatever you configure: dev, QA, UAT, staging, pre-prod, production. For each one you pick a detection mode: branch merge, CI/CD webhook, or manifest URL polling. More details on the deployment tracking page.

GitHood uses git ancestry analysis to map each merged pull request to the environments it has reached. When a new deployment lands, it figures out which PRs are included. It also catches rollbacks.

Yes. Product managers, QA, and support teams use GitHood daily to get deployment notifications and check what shipped. No git knowledge needed.

Write-only. GitHood posts to channels you select via Slack webhooks. It cannot read your messages or access other channels.

The workspace owner always counts as one seat. Additional seats are counted for each active app user and each git author with pull request activity in the last 30 days.

Yes. 14 days, full access, no feature gates. You'll need a credit card to start. Psst… use code IDDAD at checkout for an extended trial.

In France, on Clever Cloud. Fully GDPR compliant. ISO 27001 and SecNumCloud certified hosting.

No. GitHood accesses repository metadata and pull request activity only. Your source code is never read, stored, or processed. This is a deliberate design choice, not a limitation.

Yes. All data is stored in France on Clever Cloud. No data leaves the EU. ISO 27001 and SecNumCloud certified hosting. No AI processing on your data. SSO is included on all plans, and the Pro plan adds an immutable organization activity log for compliance audits.

Different goal entirely. LinearB, Jellyfish, and Swarmia are engineering metrics platforms built to measure developer productivity. GitHood gives the whole company visibility into what shipped, what's stuck, and what's deployed where. We don't read source code. We remove the need to ask for status updates, not grade people on how fast they code.

GitHood tracks deployment frequency and can surface lead time for changes as a side effect of its PR-to-environment tracking. But it is not a dedicated DORA metrics platform. If your main goal is DORA compliance dashboards, a tool like Sleuth or Faros may be a better fit. If you want the whole company to see what shipped and what's blocked without filling forms, that's GitHood.

GitHood detects rollbacks by comparing commit ancestry. When it spots one, release notifications are held automatically. Your team never gets a "deployed to production" message that turns out to be wrong. Rolled-back PRs are re-flagged with their correct environment status. See how it works on the deployment tracking page.