Jit Now Supports On-Prem and SaaS Versions of GitHub, GitLab, Bitbucket, and Azure DevOps
Published June 8, 2025.
Modern development teams work across a range of environments — some in the cloud, others in on-premise setups. Until now, security tooling hasn’t kept pace with this hybrid reality. That’s why we’re excited to announce that Jit now uses our Security Evaluation and Remediation Agent (Sera), which enables Jit to support code scanning in all environments — whether your code lives in the cloud or on-premises.
This is more than just a checkbox. This is a leap in both coverage and cost-efficiency.
What’s New: Sera Handles Code Scanning
With this release, Jit shifts code scanning responsibilities from your CI to our own infrastructure, powered by Sera. Here's what that means for customers:
1. Full SCM Coverage: SaaS + On-Prem
Previously, Jit supported code scanning in GitHub SaaS and GitLab SaaS environments. Starting today, that support expands to all versions of GitHub, GitLab, Bitbucket, and Azure DevOps — both SaaS and on-prem.
| Source Code Manager | Yesterday | Today |
|---|---|---|
| GitHub SaaS | ✅ | ✅ |
| GitHub On-Prem | ❌ | ✅ |
| GitLab Saas | ✅ | ✅ |
| GitLab On-Prem | ❌ | ✅ |
| Bitbucket SaaS | ❌ | ✅ |
| Bitbucket On-Prem | ❌ | ✅ |
| Azure DevOps Saas | ❌ | ✅ |
| Azure DevOps On-Prem | ❌ | ✅ |
This change means security teams no longer have to compromise visibility when choosing SCM architecture. Whether your organization is hybrid, cloud-native, or air-gapped, Jit now fits your workflow.
2. Zero CI Cost to Scan
Previously, customers ran scanners via their CI pipelines, which incurred usage-based charges. Now, Jit executes scans on its own infrastructure, offloading both the technical and financial overhead.
No more worrying about CI minute costs or resource spikes during peak development hours. Just consistent, reliable scanning.
How It Works (Using Bitbucket as an Example)
Onboarding a new SCM is quick and straightforward. Let’s take Bitbucket as an example. The process is nearly identical across GitHub, GitLab, and Azure DevOps.
1. Enter Your Workspace
From the Jit console, select Bitbucket and authorize access to your workspace. We support both Bitbucket Cloud and Bitbucket Server.
2. Generate a BitBucket token to complete the integration
Generate a BitBucket token and enter it in Jit’s configuration Wizard, which is all you need to implement the integration.
Once connected, select the repositories you want Jit to monitor and scan. Jit supports code scanners like SAST, SCA, secrets detection, SBOM, IaC scanning, open source license detections, and Dockerfile scanning. Enabling a scanner will automatically scan your selected repos (or full codebase), while implementing continuous scanning for every code change, so developers get immediate feedback on the security of their code.
Why This Matters
With this update, Jit delivers four big wins for AppSec, DevOps, and Engineering teams:
Code Security Everywhere You Work
Scan any repo, anywhere. Jit now covers both cloud-hosted and privately hosted SCMs, allowing organizations to standardize product security across the board.
No More CI Budget Drain
By shifting scanning workloads to Jit’s infrastructure, you can cut your CI spend without sacrificing coverage or performance.
Seamless Consolidation
Already using tools like Semgrep, Orca, or Upwind? Jit integrates them into one workflow, consolidating findings and triage into a single pane of glass.
Let’s Get Started
The shift to Sera is available to all Jit customers today. If you're already using Jit, reach out to your representative to enable support for your on-prem SCMs. If you’re not yet a customer, schedule a demo to see how Jit can simplify and scale your product security.
Security doesn’t have to be patchwork. With Jit, it’s seamless — no matter where your code lives.
