European jurisdiction by default
Servers, databases, storage, DNS, emailing and analytics are handled primarily through European partners.
Processor list
We know who touches
your data.
This continues our Proudly made in EU principle: we choose key suppliers by jurisdiction, operational control and a strict need for third parties.
Transparent supply chain
EU-first is not a slogan. It is a concrete supplier list.
Below are suppliers we use for infrastructure, emailing, analytics, form protection and payments. A specific project may use only part of this list.
The goal is not to have the longest processor list. The goal is to know each supplier's role, where infrastructure runs and whether the service should be involved at all.
8
suppliers in the core stack
Not every project uses all of them. Scope follows the actual data flows.
6
EU suppliers
Key infrastructure and operational services stay primarily under European jurisdiction.
1
self-hosted non-EU exception
We use Umami as software while analytics data remains on our own servers.
How we choose
A supplier must make sense technically and legally
For every supplier we look at operational role, jurisdiction, data location and our ability to keep critical layers under control.
Fewer third parties
We add services only when they have a clear purpose. Global platforms are not our automatic default.
Self-hosted where it adds control
When self-hosting makes sense, we run the tool on our infrastructure and separate software vendor from data custody.
Active suppliers
Who we use and why
This list describes our common operating baseline. For client projects we confirm the exact use, scope and contractual setup.
Germany + Finland
Hetzner
Jurisdiction: German supplier, primary operations in Germany, redundancy in Finland.
Role: Main infrastructure supplier.
What we use the supplier for
- Servers and compute
- Databases
- Storage
- DNS
- CDN
- Proxy layer
Control note: Primary layer for projects where we want operations, data and redundancy to remain in the EU.
France
Scaleway
Jurisdiction: French infrastructure supplier.
Role: Secondary infrastructure supplier.
What we use the supplier for
- Databases
- Storage
- Occasional server capacity
- Backup infrastructure scenarios
Control note: Used where a French EU alternative or a secondary layer outside primary hosting makes sense.
Czechia
Wedos
Jurisdiction: Czech domain and hosting supplier.
Role: Domains, DNS and smaller PHP application servers.
What we use the supplier for
- Domain registration and management
- DNS
- Servers for PHP applications
Control note: Useful for Czech domains, simpler website operations and cases where a local supplier is appropriate.
Netherlands
Lettermint
Jurisdiction: Dutch partner for email infrastructure.
Role: Main emailing partner.
What we use the supplier for
- Transactional emails
- Newsletters
- Deliverability and sender reputation
Control note: Used for operational communication where deliverability and a European partner matter.
Switzerland
Mosparo
Jurisdiction: Swiss supplier of a self-hosted form protection tool.
Role: Self-hosted spam protection.
What we use the supplier for
- Form protection
- Automated spam reduction
- Alternative to invasive CAPTCHA tools
Control note: We deploy it self-hosted, so form protection runs in an environment we manage.
USA, self-hosted in the EU
Umami
Jurisdiction: US analytics software supplier; analytics data remains on our servers.
Role: Self-hosted analytics platform.
What we use the supplier for
- Product and website analytics
- Custom event tracking
- Performance insight without marketing pixels
Control note: The exception is the software supplier outside the EU, not default storage of analytics data outside our infrastructure.
Estonia
Plausible
Jurisdiction: Estonian privacy-first analytics supplier.
Role: Analytics for projects that do not need self-hosting.
What we use the supplier for
- Website traffic
- Light conversion measurement
- Privacy-first reporting
Control note: Chosen where hosted analytics with an EU-only approach is enough and a dedicated instance is unnecessary.
Czechia
Comgate
Jurisdiction: Czech payment gateway with an EU-only approach.
Role: Payment gateway.
What we use the supplier for
- Online payments
- Payment workflow
- E-commerce and customer portal integrations
Control note: Based on supplied information, Comgate runs its own infrastructure and does not use AWS or Google Cloud.
Where context matters
We distinguish company, software and data location
Not every entry means the same kind of processing. What matters is where data actually runs and who can access it.
Umami is a US software supplier
We use it self-hosted. That means analytics data is kept on our infrastructure and Umami is not the default external data store.
The list changes by project
An e-commerce project may need a payment gateway, while a presentation website may not. SaaS can have stricter requirements for infrastructure, backups and auditability.
Want to build on the EU-first approach? Read Proudly made in EU or review your current stack with us.
FAQ
Questions about the processor list
Contact
We will review your stack and data flows.
The initial consultation is non-binding. Within 24 hours you’ll know if we’re a good fit.
- Identify which suppliers actually touch data
- Suggest EU-first alternatives
- Recommend a practical migration or adjustment plan