EU region, live

Argus is now available in the EU region with infrastructure hosted in Frankfurt. Customers can choose EU residency at the time of deployment, and customer data — including scan results, metadata, and configuration — stays within the region.

What changes

Customer deployments in the EU region are operationally identical to the US ones. Same product, same release cadence, same support model. The difference is where the data lives and which legal framework governs it. Scan metadata, classifications, lineage information, audit logs, and account configuration all remain in EU infrastructure. The control plane is replicated regionally rather than centralized.

We've also refreshed our DPA and subprocessor list to reflect the EU operational footprint, and our model contract clauses have been updated for the latest standard contractual clause framework.

Who this unblocks

This unblocks two groups of customers we've been talking to for a while. EU-headquartered companies that need GDPR-aligned data residency, where the previous answer of US-hosted with appropriate transfer mechanisms was acceptable but not preferred. And US-headquartered companies with EU subsidiaries who want regional data kept regional, particularly in financial services and healthcare where local supervisory authorities have strong opinions about cross-border data movement.

We've had a queue of these conversations. We're glad to start working through it.

Existing deployments

Existing US deployments are not affected and don't need to migrate. If your data is currently in our US region and you don't have a regulatory reason to move it, leave it. Teams that want both regions for separate business units can run them in parallel under a single account, with role-based access to each region scoped independently.