Blog

Choosing an on-premise or local-first approach for visual testing is not just a technical posture: it is a concrete answer to real constraints around sovereignty, GDPR and security. Capturing the interface of a banking intranet, an internal HR application, or an industrial monitoring dashboard produces images that may contain sensitive data — customers, employees, financial indicators. Sending them to a third-party cloud, however certified, immediately triggers a security review that many teams prefer to avoid by keeping the processing in-house.

This page gathers articles dedicated to that philosophy: differences between purely desktop solutions, on-premise deployments in a private datacenter, and private-cloud hybrids. We address the role of open source in this ecosystem (BackstopJS, Resemble.js, Pixelmatch), the trade-offs between full control and maintenance cost, the practical consequences of GDPR and sector-specific regulations (DORA, NIS2, HDS for healthcare). Delta-QA assumes a local-first architecture by default — no image leaves the machine without an explicit action — and these articles honestly explain what this choice enables and what it forbids, rather than presenting local as superior in all circumstances. For some teams it is non-negotiable; for others, a well-configured cloud remains more practical.