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.
Terraform, Nexus, Bitnami, MinIO, Redis changed their terms — you may not know where you are affected.
Scan your code, IaC and clusters read-only and match every dependency to a real change.
A ranked list with cost, risk, deadline and exit options.
Each line is a real change with a public source. We look for every place your stack depends on it.
| Tool | What changed | What we find in your stack |
|---|---|---|
| Terraform, Vault (HashiCorp) | Business Source License for future releases from August 20231; vendor now part of IBM2 | Versions in use, HCP Terraform or Vault Enterprise subscriptions, readiness for OpenTofu and OpenBao |
| Nexus Repository | Free edition became Community Edition: 40,000 components or 100,000 requests per day3 | Your edition, usage against the limits, formats you rely on |
| Bitnami images and charts | Public catalogue archived to an unsupported legacy repository; maintained images became a subscription (2025)4 | Every Bitnami image and chart referenced in your manifests, Helm values and pipelines |
| MinIO | Repository archived in April 2026; community edition source-only, no maintained binaries5 | MinIO servers and clients, versions, features in use |
| Redis | 7.4 and later moved to source-available licences in 20246; 8.0 adds AGPLv3 as an option7 | Redis versions, modules, and whether Valkey fits |
| Docker Hub | Pull limits: 100 pulls per 6 hours per IP address without login, 200 for free accounts8 | Where your CI and clusters pull from, and whether a cache sits in front |
Every affected tool: version, where it runs, which teams and pipelines depend on it.
What the change means for you: cost now and next year, security risk, deadline. Rated high, medium or low.
For each item: stay, pay, or move — with the open replacement, effort and an indicative price.
What to do first, what can wait, what to leave alone. One page.
A one-hour session with your team to go through the findings and answer questions.
If you want us to do the work, a fixed price per item. No obligation.
Shown for a typical mid-size setup. Larger platforms take longer; the scope and price are fixed on the first call.
30-minute call, read-only access to repositories and, if possible, clusters or exports.
We search code, IaC, Helm values, CI configs and image references; check versions and subscriptions.
Two short calls with the people who run the platform, to confirm what the scan cannot see.
Written report, priority plan and quote; one-hour session with your team.
Fixed price, agreed on the first call. One invoice after the report.
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.
No. Read-only access to code and, ideally, to cluster inventories is enough. We never change anything during the audit.
Then you have a written confirmation that your stack is clear, with the evidence — useful for audits and renewals. It happens rarely.
Yes. It is written so your own team can act on it.
Tell us roughly how big your platform is. We confirm the price on a 30-minute call.