GitGuardian Business vs Enterprise for Teams Running Bitbucket Server Legacy
Teams managing secrets detection on legacy Bitbucket Server installations face a narrowing support window and escalating compliance requirements. This executable path compares GitGuardian’s Business and Enterprise tiers specifically for organizations still running self-managed Bitbucket infrastructure, with version-anchored integration steps and clear boundaries on what each plan covers.
Applicability Boundary and Disclaimer
This article reports vendor documentation as of the search date. It is not security advice, legal guidance, or a substitute for your organization’s risk assessment. Configuration steps follow GitGuardian’s published documentation; verify against your specific deployment before execution.
Bitbucket Server Legacy Context
Atlassian ended support for Bitbucket Server on February 15, 2024. The vendor’s official documentation confirms that Bitbucket Data Center 9.0 was the last feature release available for Server prior to this end-of-support date. Organizations still running Bitbucket Server are operating on unsupported infrastructure with no security patches.
GitGuardian’s documentation states a minimum assured compatible version of 7.6+ for self-managed Bitbucket Server/Data Center integrations. This compatibility floor exists independently of Atlassian’s support status—GitGuardian may technically connect to your legacy instance, but the underlying platform receives no vendor security updates.
Who this tool is wrong for: Teams on Bitbucket Server versions below 7.6 cannot integrate with GitGuardian’s documented path. Organizations that have already migrated to Bitbucket Cloud should follow the separate Cloud integration workflow. Teams seeking only open-source, self-hosted secrets scanning without vendor management overhead should evaluate standalone alternatives rather than GitGuardian’s SaaS platform.
Integration Requirements (Version-Anchored)
GitGuardian documentation specifies the following for Bitbucket Server/Data Center integration:
| Requirement | Specification |
|---|---|
| Minimum assured compatible version | 7.6+ |
| Required token permissions | Read for projects, Admin for repositories |
| Integration scope | Instance-level OR project-level (mutually exclusive) |
| CI/CD scanning method | ggshield CLI wrapper |
A project-level integration can be created by any user with Administrator permissions on that project. Instance-level integration requires broader administrative access.
Back up first: Before modifying repository permissions or creating integration tokens, export your current Bitbucket Server configuration and document existing access controls. Token creation is reversible, but permission changes affecting repository access can disrupt team workflows.
Business Plan: Capabilities and Limits
The vendor’s official pricing page and documentation establish Business as the growth-tier plan. Key characteristics sourced from official material:
- Trial period: 30-day free trial of Business plan features available
- Pricing model: Priced per active committer on monthly or annual basis
- Contributor definition: A contributing developer is defined as a commit author email address that made at least one commit to a private collaborative repository within the last 90 days
Business plan features include core secrets detection for git repositories, push protection, and standard remediation workflows. The plan targets growing organizations moving beyond individual developer monitoring.
Business plan constraints relevant to Bitbucket Server legacy environments:
- No NHI Governance module (vault coverage, identity inventory, OWASP policies)
- No AI-powered remediation tools (AI Copilot, Smart Routing)
- No enterprise data source coverage (file storage, CI logs, collaboration tools beyond git)
For teams on legacy Bitbucket Server, this means secrets detection operates at the repository level only. CI pipeline scanning requires manual ggshield CLI integration rather than native platform hooks. Non-human identity governance—critical for organizations with extensive service accounts and API keys—requires Enterprise tier.
Enterprise Plan: Add-Ons and Complex Environment Support
The vendor’s official pricing page lists Enterprise as built for complex environments with capabilities that mature security programs require. Documented Enterprise add-ons include:
| Capability | Business | Enterprise |
|---|---|---|
| Core secrets detection | Included | Included |
| NHI Governance (vault coverage, identity inventory, OWASP policies) | Not included | Included |
| AI-powered remediation (AI Copilot, Smart Routing) | Not included | Included |
| Enterprise data sources (file storage, CI logs, collaboration tools) | Not included | Included |
| Enterprise trial | Not specified | Included |
Published third-party benchmarks report that customers achieved significant reductions in MTTR and remediated substantially more secrets with advanced remediation capabilities—though these figures aggregate across all customer deployments, not specifically Enterprise tier or Bitbucket Server environments.
Bitbucket Server Specific Integration Path
For teams proceeding with GitGuardian on legacy Bitbucket Server 7.6+, the documented integration sequence follows GitGuardian’s current documentation:
- Prerequisite verification: Confirm Bitbucket Server/Data Center instance is accessible from GitGuardian’s SaaS platform or your self-hosted GitGuardian deployment
- Token generation: Create token with Read permissions for projects and Admin permissions for repositories
- Scope decision: Choose instance-level (all repositories) or project-level (specific project) integration—this selection is mutually exclusive per GitGuardian documentation
- ggshield CI configuration: For pipeline scanning, install ggshield CLI and configure with GitGuardian API key
Version anchor: These steps follow GitGuardian’s current published documentation for Bitbucket Server/Data Center integration. The 7.6+ minimum compatibility version has remained consistent across documentation versions reviewed.
Migration Path: Business to Enterprise
Organizations starting on Business and requiring Enterprise capabilities follow this documented path:
- Assessment phase: Identify which Enterprise features are required—NHI Governance for service account sprawl, AI-powered remediation for team scaling, or enterprise data sources for compliance scope expansion
- Contributor audit: Review contributing developer count against 90-day commit history, as Enterprise pricing is customized for large deployments per vendor documentation
- Trial activation: Enterprise trial is included per the vendor’s official pricing page—activate to validate feature fit before commitment
- Configuration migration: Existing Bitbucket Server integrations and ggshield configurations transfer; NHI Governance and enterprise data sources require additional connector deployment
Back up first: Before migrating plan tiers, export all existing incident data, custom policies, and team configurations. Plan tier changes should not affect historical scan data, but documentation of current state enables rollback verification.
Who Should Choose Which Tier
Business plan fits when:
– Team size and commit volume align with per-active-committer pricing
– Core secrets detection and push protection satisfy current compliance requirements
– Bitbucket Server integration is primarily for repository scanning, not broader data source coverage
– Manual remediation workflows are acceptable given incident volume
Enterprise plan fits when:
– NHI Governance is required for service account and vault coverage
– AI-powered remediation is needed to scale incident response
– Compliance scope extends to file storage, CI logs, and collaboration tools beyond git
– Organization size triggers customized pricing rather than standard per-committer rates
Neither tier fits when:
– Bitbucket Server version is below 7.6 (integration unsupported)
– Organization requires fully air-gapped deployment without SaaS connectivity
– Budget constraints prohibit per-committer pricing models entirely
Execution Checklist for Bitbucket Server Legacy Teams
| Step | Action | Verification |
|---|---|---|
| 1 | Confirm Bitbucket Server version ≥ 7.6 | Server admin console |
| 2 | Export current configuration and permissions | Backup verification |
| 3 | Generate integration token with required permissions | Token test in GitGuardian UI |
| 4 | Select instance-level or project-level scope | Document decision rationale |
| 5 | Configure ggshield for CI/CD pipelines | Test pipeline execution |
| 6 | Evaluate 30-day Business trial or Enterprise trial | Feature coverage assessment |
| 7 | Plan tier migration if Enterprise features required | Contributor count audit |
Final Boundary Conditions
The February 15, 2024 end-of-support date for Bitbucket Server is fixed and unchangeable. GitGuardian’s 7.6+ compatibility does not extend Atlassian support. Organizations running legacy Bitbucket Server should treat secrets detection as one component of a broader migration strategy, not a substitute for platform modernization.
Published third-party analysis notes that GitGuardian’s strength on coverage breadth creates trade-offs against specialized alternatives on specific dimensions. Teams with deep entropy analysis requirements or preference for fully open-source tooling should evaluate whether GitGuardian’s breadth aligns with their specific technical priorities.
For current pricing specifics beyond the per-active-committer model and customized Enterprise rates described in vendor documentation, consult GitGuardian’s official pricing page directly. Figures not present in the verification material are omitted per policy.
Visit GitKraken’s official site
Summary Table: Business vs Enterprise for Bitbucket Server Legacy
| Factor | Business | Enterprise |
|---|---|---|
| Bitbucket Server 7.6+ integration | Supported | Supported |
| Core secrets detection | Included | Included |
| Push protection | Included | Included |
| NHI Governance | Not included | Included |
| AI-powered remediation | Not included | Included |
| Enterprise data sources | Not included | Included |
| Pricing structure | Per active committer, monthly/annual | Customized for large deployments |
| Trial availability | 30-day Business trial | Enterprise trial included |
