Home›Services›Snyk / SonarQube exit

Replace your commercial scanner without starting from zero

Leaving Snyk or SonarQube is not hard because of the scanning. It is hard because of what your team built around it: rules, accepted risks, quality gates, history. We move those to an open set-up in GitLab and run old and new side by side until the numbers match.

from $6,000 · fixed price Measured first, then fixed price and dates Side-by-side comparison
The problem

Scanner licences grow per developer while you use a fraction of the product.

What we do

Move rules, exceptions and history to open scanners in GitLab.

The result

Two weeks side by side, then you switch with data, not hope.

Is this you?

What replaces what

Open tools are not identical to commercial ones. That is why we compare results before you switch off the old tool.

Commercial scannerpriced per developer or project
Open tools in GitLabon your infrastructure
Dependency scanningknown vulnerable libraries
Trivy + Dependency-Trackkeeps watching released versions
Container scanningvulnerable OS packages
Trivyin CI and on your registry
Code analysiscustom and built-in rules
Semgrep CE or Opengrepyour rules rewritten and tested
Quality gateswhat blocks a merge
GitLab MR rules + lintersthresholds agreed with the team
Findings and historyignores, accepted risks
DefectDojoimported where export allows

What you get

Inventory of use

Which features, rules, gates and integrations you actually use today.

Open set-up

Scanners in your GitLab CI and the findings platform, running on your infrastructure.

Rules and exceptions moved

Custom rules re-written, accepted risks carried over with owner and expiry.

Comparison report

Two weeks of old and new results side by side: what each finds, what differs, and why.

Switch-off

Old tool removed from pipelines once you are satisfied.

How it goes

The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.

  1. Step 1 · 1–3 days

    Inventory

    Features and data in use; export of findings and settings; final fixed price.

  2. Step 2

    Build

    Open scanners and DefectDojo set up; rules and exceptions moved.

  3. Step 3

    Side by side

    Both run on the same projects; differences analysed and tuned.

  4. Step 4

    Switch

    Old tool removed; handover.

What we need from you

  • Admin access to the current tool for export.
  • Maintainer access to GitLab groups in scope.
  • A security owner to approve rule changes and accepted risks.

Not included

  • Contract or licence negotiations with your current vendor.
  • Fixing findings in your code.
from $6,000

Fixed price after the measurement in step 1. Paid by milestone.

What changes the price

  • Number of projects and languages.
  • Custom rules and quality gates to rewrite.
  • History you need to keep.

Questions teams ask

Will we lose coverage?

Some findings differ between tools in both directions. The side-by-side run shows exactly where, so you decide with data.

Can we keep our finding history?

We import what the old tool lets you export. For audit, we also archive the original exports.

What if we only want to replace part of it?

That works. Many teams replace dependency and container scanning first and decide on code analysis later.

Often done together

Tell us which tool and how many projects

We give you a price range on a 30-minute call.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Book a 30-minute call