Your client knows they received exactly what left your process.
Every software release carries a digital signature the client can check on their own.
Control over what your software is built from — and proof that the package at the client came out of your process.
Your client checks where the package came from without asking you for a statement.
Most of your product is code you didn't write.
Most of your product is someone else's code. No one has to attack you directly — a library or a tool you use is enough. One compromised element reaches everyone who downloads it, along with the update.
We define the scope after an assessment — starting with the element that lowers your risk fastest.
You know what your product is built from.
We generate the bill of materials automatically with every release, not by hand once a year — so the question "do you use this library" stops being a week-long project. We sign artifacts so the client can independently verify they received what came out of your process. New dependencies pass a check before they enter the project, because the cheapest moment to reject a risky library is before it is added. We arrange the whole thing to close the technical layer of the CRA requirements.
Each stage leaves you with a concrete result, not meeting notes.
An SBOM generated automatically with every release, not once a year by hand.
ResultAn SBOM generated automatically with every release
The client can verify they received what came out of your process.
ResultSigned artifacts your client can verify on their own
A new library passes a check before it enters the project.
ResultRules for accepting new dependencies, built into code review
Technical documentation and the ability to respond to a vulnerability report.
ResultTechnical documentation and a vulnerability reporting procedure for the CRA
Your client knows they received exactly what left your process.
Every software release carries a digital signature the client can check on their own.
“Do you use this library?” becomes a single search.
Every release comes with a list of all the libraries it is made of.
Templates and roles are agreed before the first report is due.
Everyone knows who reports a vulnerability, to whom, by when and using which template.
We define the scope after a call and an assessment. Smaller engagements close in a few weeks; larger ones we split into stages, so the result is visible after the first.
Usually not to all of it. In most cases access to the build pipeline configuration and organization settings is enough. We define the scope in writing before we start.
Yes, but not full time. We need contact with someone who knows the system, and a review of our changes. The rest is on us.
Not entirely. We cover the technical layer: the bill of materials, release signatures, artifact provenance and the vulnerability reporting process. Full CRA compliance also requires organisational and legal measures, and our work does not replace a legal opinion or a formal audit.
We plug into what already works for you. Replacing a tool is the most expensive and least often necessary way to improve security.
No. We work with standards and tools your team knows or will quickly learn. Everything is documented and handed over.
We wire controls so they run in the background. If one starts blocking work, we tune it or move it to a different point in the process.