Frigga Blogs

Ask a team how they roll back and many will say they re-run the pipeline on the previous commit. That is not a rollback. Even with identical source code, a rebuild can produce a different artefact, because dependencies, base images, and buil…

The promise of a staging environment is simple and appealing: it is a near-copy of production, so if your change works there, you can be confident it will work in production ( All Quiet, 2026 ). That confidence is the problem, because stagin…

Most teams can recite the four DORA metrics and could not tell you their own. The usual reasons are that measuring them sounds like a project, or that it means buying a platform. Neither is true if you deploy through GitHub, because the data…

Ask most teams to show you exactly how their production environment is configured, and the honest answer is that they cannot, because the only complete record of it is the running system itself. The real state lives in the cluster and in the…

You scan your code for vulnerabilities and you lock down what runs in your cluster, but the pipeline in between, the thing that turns your source into the artifact you deploy, is usually wide open. Nothing along that path proves that the ima…

There is one deploy your team cannot simply roll back, and it is the one that touches your database. Every other change has an undo: revert the code, redeploy the old version, and you are back where you started. A migration does not work lik…