Home›Services›Open Source Exposure Audit

Find out which licence changes will hit your stack — in one week

In the last three years, many tools DevOps teams rely on changed their licence, price or support. We find where they sit in your stack, what each change means for you in money and risk, and what an exit would take. You keep the report either way.

from $1,800 · fixed price Scope fixed on the first call Read-only access
The problem

Terraform, Nexus, Bitnami, MinIO, Redis changed their terms — you may not know where you are affected.

What we do

Scan your code, IaC and clusters read-only and match every dependency to a real change.

The result

A ranked list with cost, risk, deadline and exit options.

Is this you?

What we check

Each line is a real change with a public source. We look for every place your stack depends on it.

ToolWhat changedWhat we find in your stack
Terraform, Vault (HashiCorp)Business Source License for future releases from August 20231; vendor now part of IBM2Versions in use, HCP Terraform or Vault Enterprise subscriptions, readiness for OpenTofu and OpenBao
Nexus RepositoryFree edition became Community Edition: 40,000 components or 100,000 requests per day3Your edition, usage against the limits, formats you rely on
Bitnami images and chartsPublic catalogue archived to an unsupported legacy repository; maintained images became a subscription (2025)4Every Bitnami image and chart referenced in your manifests, Helm values and pipelines
MinIORepository archived in April 2026; community edition source-only, no maintained binaries5MinIO servers and clients, versions, features in use
Redis7.4 and later moved to source-available licences in 20246; 8.0 adds AGPLv3 as an option7Redis versions, modules, and whether Valkey fits
Docker HubPull limits: 100 pulls per 6 hours per IP address without login, 200 for free accounts8Where your CI and clusters pull from, and whether a cache sits in front

What you get

Inventory

Every affected tool: version, where it runs, which teams and pipelines depend on it.

Exposure per item

What the change means for you: cost now and next year, security risk, deadline. Rated high, medium or low.

Exit options

For each item: stay, pay, or move — with the open replacement, effort and an indicative price.

Priority plan

What to do first, what can wait, what to leave alone. One page.

Walk-through

A one-hour session with your team to go through the findings and answer questions.

Fixed quote

If you want us to do the work, a fixed price per item. No obligation.

How it goes

Shown for a typical mid-size setup. Larger platforms take longer; the scope and price are fixed on the first call.

  1. Day 1

    Kick-off and access

    30-minute call, read-only access to repositories and, if possible, clusters or exports.

  2. Day 2–3

    Scan

    We search code, IaC, Helm values, CI configs and image references; check versions and subscriptions.

  3. Day 4

    Interviews

    Two short calls with the people who run the platform, to confirm what the scan cannot see.

  4. Day 5

    Report and walk-through

    Written report, priority plan and quote; one-hour session with your team.

What we need from you

  • Read-only access to Git repositories (or an export).
  • Read-only access to clusters or a list of running images, if you can share it.
  • Two people for short interviews: platform and security or procurement.

Not included

  • Legal opinions on licences — we describe what changed and point to the source; your counsel interprets.
  • Fixing anything during the audit.
  • Application dependencies (npm, Maven libraries) — that is a separate software composition review.
from $1,800

Fixed price, agreed on the first call. One invoice after the report.

What changes the price

  • Number of repositories and clusters.
  • Environments — one platform or several separate ones.
  • Access — direct read-only access is faster than working from exports.

Questions teams ask

Is this legal advice?

No. We tell you what changed, with the vendor's own source, and what it means technically and financially. If a licence question matters for your business, take the report to your counsel.

Do you need production access?

No. Read-only access to code and, ideally, to cluster inventories is enough. We never change anything during the audit.

What if we find nothing?

Then you have a written confirmation that your stack is clear, with the evidence — useful for audits and renewals. It happens rarely.

Can we use the report without hiring you?

Yes. It is written so your own team can act on it.

Other starting points

Start with one week and a clear list

Tell us roughly how big your platform is. We confirm the price on a 30-minute call.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public announcements, documentation and legal texts, for orientation only; not legal advice. All trademarks belong to their owners.
  1. HashiCorp: HashiCorp adopts Business Source License (Aug 10, 2023)
  2. IBM Newsroom: IBM completes acquisition of HashiCorp (Feb 27, 2025)
  3. Sonatype Help: Usage Center — Community Edition usage limits
  4. Broadcom Community: How to prepare for the Bitnami changes (Aug 18, 2025)
  5. GitHub: minio/minio repository (archived Apr 25, 2026)
  6. Redis: Redis adopts dual source-available licensing (Mar 20, 2024)
  7. Redis: Licenses
  8. Docker Docs: Docker Hub usage and limits
Book a 30-minute call