New · Release 2026.04, Multi-tenant audit exports & SLA dashboards now liveSee changelog →
DevOps governance
Git governance, access, repository, and security views
Manage provider configuration, repository visibility, user access, analytics, and security posture.
Product illustration · sample data
Platform Security
18/18 evidence
RLS2FAAudit logsCompliance
9.3/10
DIY assurance score · verified May 2026
Tenant tables with RLS10
Privileged roles · 2FAEnforced
Immutable audit eventsLive
Security controls verified18/18
Product proof
Already live in the product
Backed by app modules
Running in production today: the Git dashboard, provider configuration, repository management, user management, security posture, and access control.
Protected app route: /git-dashboard
How it works
Built around real workflows
Highlights below describe capabilities already present in the protected app behind this page.
Git provider configuration
Repository management
User and access views
Security posture analytics
Workflow
What teams can do here
Step 1
Connect providers
Step 2
Review repositories
Step 3
Audit access
Step 4
Track security posture
How it works
How it works
01
Connect a Git provider
Add a provider configuration for GitLab, GitHub, Bitbucket, Gitea or Azure DevOps with a personal access token. The token is encrypted at rest with a per-tenant key, not stored in plaintext.
02
Sync repositories and people
A scheduled sync (30 minutes by default) pulls repositories, groups, members, merge requests, issues and pipelines into a tenant-scoped read-only cache, so the dashboard loads without hammering the provider API.
03
Review who can reach what
The access report and project access matrix show every user and their access level per repository, so Maintainer and Owner rights are visible in one place instead of buried in provider settings.
04
Surface security posture
See who has no two-factor enabled, list dormant accounts, and run a privileged-access review of Maintainer/Owner grants. An MFA reminder can be emailed to users still missing 2FA.
05
Track delivery analytics
Activity stats, contribution trends, language distribution, code-quality and DORA-style metrics turn raw commit and pipeline data into a governance view for the whole tenant.
Example
A worked example
Say a software agency with forty developers is spread across GitLab and a legacy GitHub org. After connecting both providers, the access matrix shows nine people still holding Maintainer rights on repositories they no longer touch, and six accounts with no commits in ninety days. The team runs the privileged-access review to walk each grant down, emails the 2FA reminder to the eleven users still missing two-factor, and leaves the sync on its half-hour cadence so next quarter's audit starts from a current picture instead of a stale export.
FAQ
Frequently asked questions
Which Git providers can I connect?
GitLab, GitHub, Bitbucket, Gitea and Azure DevOps. Each provider is added as its own configuration with its own token, and several can run side by side in one tenant.
Does connecting a provider change anything in it?
No. The sync is read-only — it pulls repositories, members, merge requests and pipelines into a cache for reporting. The one action that reaches out is the optional MFA reminder, which emails users who have no 2FA asking them to enable it; it does not flip the provider setting for them.
How is the provider access token protected?
It is encrypted before it is stored. When the configuration is bound to a tenant it uses a per-tenant Fernet key; otherwise it falls back to the platform credential vault. The plaintext token is never serialized back out.
How current is the dashboard data?
Each provider syncs on an interval you set — 30 minutes by default — and you can trigger a manual sync at any time. The dashboard reads the cached copy so it stays fast even for large orgs.
Can I find inactive or over-privileged accounts?
Yes. The dormant-accounts view lists users with no recent activity, and the privileged-access review lists everyone holding Maintainer (level 40) or Owner (level 50) access across projects, so you can right-size grants during an audit.
Does Infronest store a copy of our source code?
No. The sync caches governance metadata — repositories, groups, members, branches, merge requests, issues, pipelines and commit records — not your codebase. Your code stays with your Git provider.
What delivery and quality analytics come out of the box?
Activity statistics, contribution trends, language distribution, code-quality views and DORA-style delivery metrics, all computed from the synced repository, commit and pipeline data for your tenant.
Connect GitLab, GitHub, Bitbucket, Gitea or Azure DevOps and get one read-only access matrix — with dormant accounts, missing 2FA and Maintainer/Owner grants surfaced for review.