Deploy the full Thunders platform in your cloud or datacentre. Your source code, test data, and screenshots stay inside your perimeter.


Deploy AI test automation without pushing your source code, test data, or screenshots to a vendor cloud. Keep everything inside the perimeter your compliance team already approved.
Your tests, test data, and screenshots stay in the region your compliance team already approved.
Azure OpenAI, OpenAI, Anthropic, Gemini or OVH AI Endpoints. Route AI calls through providers your legal team has already vetted.
Sign-in runs end-to-end through Entra ID. Access maps to the groups you already manage. No open signup.
Azure, AWS, GCP, Kubernetes, or Docker. Your platform team picks the orchestrator.
Full self-hosting for teams that need everything inside their perimeter. Browser Engine via Azure Relay for teams that only need the engine locked down.
Compatible with HIPAA, SOC 2, and GDPR requirements. Deployed in production by enterprises with strict data residency mandates.
Pick the model that matches your infrastructure and your compliance requirements. Compare the two below and pick the one that fits.
The whole platform runs in your infrastructure. Thunders ships container images. Your team runs them on your cloud or on-prem.
Your infrastructure handles everything. Thunders never sees your data. Updates ship through a dedicated container registry on the cadence that fits your change management.
Enterprises with data residency requirements, non-Azure infrastructure, or a policy that platforms must live inside their own perimeter.
Microsoft Entra ID, an email transport (SendGrid or SMTP), object storage (Azure Blob or S3-compatible), and at least one LLM provider.
Only the browser engine runs on your side. The Thunders cloud handles orchestration. The engine reaches us through outbound HTTPS.
The Thunders cloud orchestrates the tests. Your QA environments never touch the public internet. Bring your own Azure Relay namespace, or use ours.
Organisations with HIPAA, SOC 2, GDPR, or data sovereignty constraints that cannot expose QA environments to the internet, but do not need the full platform on-prem.
Docker and an outbound HTTPS (443) connection. Optionally, your own Azure Relay namespace if you would rather own the transport.
The environments and mandates that push teams to move the platform inside their own network.
For enterprises where the answer to “where does the data go” needs to be “nowhere else.” Full self-hosting keeps every test artefact, screenshot, and log inside your network.
Point Thunders at OVH AI Endpoints or your own Azure OpenAI tenancy. Keep prompts and generated tests inside the jurisdiction your regulator cares about.
Applications that live behind a VPN, in a private datacentre, or on infrastructure that cannot be IP-whitelisted still get automated coverage. The browser engine relay reaches them without opening a single inbound port.
Thunders ships as container images. Your platform team picks the orchestrator and the update cadence. No new vendor cloud to onboard.
