Service
DevSecOps consulting
A well-designed pipeline catches a vulnerability, a forgotten secret or a vulnerable dependency before it reaches production, not after. We design or take over your CI/CD pipelines so that security is part of them from the start, without slowing your developers down.
What we set up
- CI/CD pipelines: GitLab CI, GitHub Actions, Forgejo Actions. Reproducible builds, tests and deployments.
- Code and dependency analysis: static analysis (SAST), vulnerable dependencies (SCA), secret detection, container image scanning.
- Supply chain: SBOM, signed commits and artefacts, protected branches, mandatory review.
- Secrets: out of the code and out of plain-text variables, with SOPS, Vault or OpenBao.
- Self-hosted runners in Europe: your code does not go through third-party machines.
Our method
- Audit of the existing pipeline and practices.
- Prioritised plan: what reduces risk the most comes first.
- Gradual rollout. Checks start in warning mode, then become blocking once false positives are sorted out, so teams are never stuck.
- Handover: documentation and training. You stay in control of your pipelines.
Why now
NIS2 requires securing the supply chain, and the Cyber Resilience Act will require software vendors to handle vulnerabilities and provide an SBOM. A well-equipped pipeline is the simplest way to meet both.
Why us
Over ten years of DevOps and DevSecOps engineering, and contributions to open-source projects used at very large scale, where every change goes through this kind of pipeline.