Bulk
Platform / Data residency & hosting

Your data, your country.

You choose the country. Your data lives there — live records, backups, logs and files — and it doesn't leave without your written permission. Eight regions across three continents, on European-operated infrastructure. Never a hyperscaler.

United Kingdom Germany France Poland Canada Singapore Australia United States New
Two plans, one standard of care

Which plan? One question.

Does a specific country have to appear on your contract? Every customer gets the same encryption, backup, audit and export protections — the difference is where the server lives, and whether you share the hardware.

Standard

Hosted in Germany, EU sovereign.

The default for most customers. Your deployment lives on European-operated infrastructure in Germany — GDPR-compliant, with every baseline protection. Right for any obligation that says "EU" or "GDPR" rather than a named country.

  • European-operated, GDPR-compliant by default
  • Single-country data & backups, full audit trail
  • Encrypted in transit and at rest
Enterprise

Your own dedicated node, in the country you choose.

For customers whose end-clients mandate a specific country — defence, aerospace, regulated labs. You get your own dedicated Bulk node in any of eight regions, including the United States, plus a written Data Residency & Processing Statement on Bulk letterhead.

  • One node, one customer — never shared hardware
  • Residency statement, DPA & sub-processor list
  • Any of eight regions, the US included
If the requirement is "EU", "GDPR-compliant" or "European hosting" — Standard is enough. If the contract names a specific country, or uses phrases like "US-only", "non-US" or "defence-approved jurisdiction" — Enterprise is the fit. Unsure? Send us the clause and we'll confirm.
Eight countries, three continents

Pick the country that suits your obligations.

Every deployment lives in exactly one country below. Once chosen, your data doesn't move unless you explicitly authorise it.

Europe

United Kingdom

London · Erith
UK

UK customers, defence supply chains and end-clients requiring UK residency — UK MoD, aerospace primes.

Germany

Limburg
EU · Default

Default European region. Suited to any EU-residency requirement.

France

Gravelines
EU

French customers and French public-sector clients.

Poland

Warsaw
EU

Central and eastern European operations.

Americas & Asia / Oceania

Canada

Beauharnois
Non-US

Non-US hosting for Canadian federal contracts, or customers wary of US data law.

United States

OVHcloud US
New

US residency for domestic federal contracts, ITAR-adjacent supply chains or US-only mandates.

Singapore

Singapore
On request

APAC operations. Available on request; standard provisioning lead time.

Australia

Sydney
On request

Australian customers and Oceania supply chains. Available on request.

Need a country that isn't listed? New regions in Asia, Oceania or the Americas can usually be added with a short lead time — talk to us about the specific country.

What every deployment includes

The same protections, in every region.

Choosing a region is the visible part. Underneath, every deployment — UK, EU, Canada, US or otherwise — ships with the same six baseline protections. These are the answers to your supplier-assurance questionnaire.

Primary data stays in-country

Your database, file attachments, search indexes and audit logs all live on a server inside the country you chose. No copies abroad unless you authorise it in writing.

Granular recovery, 6-month history

Hourly snapshots for the first 72 hours, six-hourly to day 7, then daily for six months — stored in your region, encrypted before they leave the database.

European-operated hosting

Your live system runs on Hetzner in Germany and OVHcloud across the UK, Europe, Canada and the United States — not a hyperscaler.

Encrypted in transit & at rest

All client traffic over TLS, disk-level encryption on the server, and backups encrypted before they leave the database. Industry-standard across the board.

Enterprise only

Your own dedicated node

Enterprise customers run on their own node. One node, one customer — your data and another customer's never share the same machine.

Complete activity log

Every record change, login, export and configuration change is logged with a tamper-evident timestamp. Exportable on request for internal or external audit.

No big-tech cloud

Off the hyperscalers. On your terms.

A worry we hear a lot: “whose cloud is our data actually on?” With Bulk it's never a big-tech hyperscaler — it's independent infrastructure in the country you choose, US included.

Where it runs

Independent infrastructure, in the country you choose.

Not AWS, Azure or Google Cloud — Bulk runs on established independent providers, in the region you pick. Need to stay in Europe? You stay in Europe. Need US soil for a US contract? We host you in the US. You hold the jurisdiction, not a big-tech cloud.

You pick the countryISO 27001 & SOC 2 facilities
Where AI fits in

AI that helps, without holding your data.

Bulk's AI runs in your own region and is built to forget — it reads, responds, and keeps nothing. Your records are never used to train it, and nothing leaves the boundary you chose.

In your regionNo trainingNothing retained
Enterprise In the contract, not just the brochure

What we put in writing.

Standards describe how the platform works; commitments describe what we agree to as part of your Enterprise contract — the items your legal and procurement teams look for, on the page so there are no surprises.

Full sub-processor list

On request we share the complete list of third parties that touch your deployment — hosting operator, email delivery, error-tracking. We notify you in advance of adding any new one, so there are no hidden parties.

Standard DPA at onboarding

A GDPR-aligned Data Processing Agreement is signed as part of onboarding — naming Bulk as processor and you as controller, covering data-subject rights, transfers and breach-notification obligations.

72-hour breach notification

In the unlikely event of an incident affecting your data, you're notified within 72 hours — aligning with GDPR Article 33. Reports include scope, affected data categories and our remediation timeline.

Clean exit, verified destruction

On cancellation: a 30-day grace period with a full export in standard formats (CSV, JSON, original files). After export, the node and all backup tiers are wiped on an agreed schedule — with a written destruction certificate on request.

Your legal team receives a short pack — the Data Residency & Processing Statement, a signed DPA, the sub-processor list and the incident-notification clause. That's usually enough to clear supplier-assurance review at most regulated end-customers, including defence, aerospace and pharma.
From procurement, IT & compliance

The questions we're usually asked.

01 Our customer requires data hosted exclusively in their country. Can Bulk meet that?

Yes. Pick the matching region from the eight available — live data, backups and logs all stay in-country, and we'll issue a written statement for your customer.

02 Can different customers be hosted in different regions?

Yes — on Enterprise. Each customer gets their own dedicated node in their own region. The region is a property of your deployment, not the platform. Standard customers share Germany.

03 Are you using AWS, Azure or Google Cloud underneath?

Not for hosting. Your system runs on independent European providers, in the region you choose — including the US for US contracts. The big-tech clouds are only ever used for AI inference, in your own region, with no training on your data and nothing retained.

04 What if our regulator requires audit access to the data centre?

Our hosting partners operate certified, audit-ready facilities (ISO 27001 and SOC 2). We'll provide the certifications and documentation your regulator needs.

05 Where are backups stored, and how long are they retained?

Hourly for 72 hours, six-hourly to day 7, then daily for six months. Snapshots are encrypted and kept in the same country as your live system — never cross-border.

06 What happens to our data if we leave Bulk?

A full export in standard formats (CSV, JSON, original files). The deployment is decommissioned; the server and backups are wiped on an agreed schedule.

07 Can you support a region that isn't in your current list?

Often, yes. New regions in Asia, Oceania or the Americas can usually be added with a short lead time. Talk to us about the specific country.

08 How long does it take to stand up a new deployment?

From order to live system: usually 5 working days — infrastructure, application setup, hardening and customer configuration.

Enterprise How to proceed

You brief us once. We handle the rest.

Hosting a regulated system in a specific country can feel like a lot of paperwork — it isn't when we're doing the lifting. Here's the whole path, from first email to live system.

01

Share your obligations

One short email: which country (or countries) you must host in, and why — customer mandate, regulator, internal policy. That's the only input we need.

02

We draft the statement

Within 48 hours we send a draft Data Residency & Processing Statement on Bulk letterhead, tailored to your region.

03

We bundle the pack

The statement, DPA, sub-processor list and order form in one self-contained pack, pre-filled with your details. No drip-feed across the week.

04

PO confirmed

Once your PO is issued, we confirm receipt and proceed straight into provisioning. No waiting room, no extra cycles.

05

We provision your node

We order and configure your dedicated node in the chosen country — hardware, OS, database, backups, monitoring. Nothing for your IT team to stand up.

06

Go-live & walk-throughs

Your subdomain goes live, users are invited, and we run first-week walk-throughs. Usually 5 working days, end to end.

Your Enterprise subscription includes the dedicated node and the region of your choice from the eight listed — no hidden line-items, no per-region upgrades. Bespoke regions outside the current list are priced separately on request.

Send us the clause. We'll confirm the plan.

Tell us the country you need on the contract — or paste the residency requirement — and we'll come back with the region, the statement and a go-live date.