From a GitHub organization to a team dashboard, in four steps and under ten minutes.
Here is exactly what Squadlog connects to, what it reads, what it keeps, what it writes, and what it never does. No marketing, the actual mechanics.
Install a read-only GitHub App.
Squadlog is a GitHub App, not a personal token. You install it on one or several GitHub.com organizations, or on a GitHub Enterprise Server 3.12+ instance, and choose which repositories it may see. GitHub then pushes events to Squadlog as they happen: commits, pull requests, reviews, merges.
- Read access to repository metadata, commits and pull requests
- Read access to the members of the organization
- No write access, anywhere. No access to issues, discussions or secrets.
- Webhooks are verified by signature; a connection that stops sending events is flagged within the hour.
A name, a color, its repos, its managers.
A Squadlog team is yours, not GitHub’s. Pick the repositories it works on across any connected organization, name its managers, and choose its primary measure: merged pull requests for teams that review everything, commits for teams that push to main. Both are always tracked.
- One repository can belong to several teams; one person can be in several teams
- History loads in the background: 12 months
- Thresholds, working days and time zone are set per team and can change any time
The team fills itself. Nobody signs up.
Everyone who contributes to a tracked repository appears as a member. Several GitHub logins can be merged into one person, across organizations. Each linked member receives an information email describing what is tracked, what is not, and their rights. Developers never need a Squadlog account.
- Logins detected from commits and PRs, matched to people by the manager
- Declared absences pause the inactivity alert and are excluded from working-day counts
- Effort scores and rankings seen by managers only, no automated decision
Each commit is read once, then forgotten.
When a commit lands or a PR merges, Squadlog loads the diff in memory, has it read by a model running on its own servers, writes one line a non-technical reader understands and scores the effort from 1 to 10. The summary and the score are kept. The diff is discarded. That is the only moment Squadlog touches code.
- Own models, own servers: nothing goes to a third-party AI provider, nothing is used for training
- Excluded repositories are never read, even at merge; members can opt out
- Everything else (dashboards, alerts, reports) is computed from metadata only
The whole data story on one card.
What a manager actually sees, day by day.
Ten minutes from now, your first team is on the dashboard.
7 days free, every feature. No credit card. Developers never need an account.