Iteration Layer
Products
Use Cases
Resources
Pricing
Documentation navigation

EU Hosting & Subprocessors

Iteration Layer publishes hosting and provider boundaries so European teams can review where workflow data is processed.

Where Does Iteration Layer Run Core Infrastructure

Core Iteration Layer application and API infrastructure runs on EU-hosted infrastructure.

The primary cloud infrastructure provider is Hetzner Online GmbH in Germany. This covers the main application and API infrastructure used to receive, authenticate, process, and respond to customer requests. Hetzner’s data centers and cloud services are covered by ISO/IEC 27001:2022 and BSI C5:2020 Type 2.

Which Subprocessors Are Used

Iteration Layer uses subprocessors for infrastructure, billing, email, monitoring, and AI inference where a product flow requires it.

Provider Purpose Data Touched Location Notes
Hetzner Online GmbH Cloud infrastructure and DNS Application data, account data, logs, transient processing workload Germany, EU
Stripe, Inc. Payment processing Billing identifiers, subscription data, payment metadata United States, with transfer safeguards described in Privacy Policy
Google LLC AI model inference where product flow requires it Submitted content routed for inference when required Regional processing is configured for supported flows; review Responsible AI Use
Lettermint B.V. Transactional email and optional product updates Email addresses, email event metadata, unsubscribe and suppression data Netherlands, EU
OpenStatus SAS Uptime monitoring External health-check metadata France, EU, with non-EEA monitoring regions where applicable

For the formal public list, see the Privacy Policy.

What Does EU-Hosted Mean Here

EU-hosted means the core Iteration Layer application and processing infrastructure is hosted in the European Union.

This does not mean every supporting provider is an EU company. Billing, email, monitoring, and AI inference may involve their own provider locations, contracts, and transfer safeguards. Review Privacy Policy when your workflow has strict residency or procurement requirements.

How Should Sovereignty-Sensitive Teams Review This

Sovereignty-sensitive teams should review the full workflow path, not only the primary API host.

For each workflow, check which API is used, whether AI inference is involved, whether webhook delivery sends results to your own infrastructure, and whether downstream tools store generated outputs. Iteration Layer reduces the processing-layer surface area, but your complete workflow may still include storage, automation, review, and delivery systems outside Iteration Layer.

How Are Subprocessor Changes Handled

Privacy Policy is the public source of truth for current subprocessors.

Use this page as a technical summary, then rely on Privacy Policy and Data Processing Agreement for formal legal language.