Someone just booked an audit
Sharon Lijo in Germany · Remote · CET

Local-first, because compliance will ask.

German engagements start with the data question, not the feature list. Modules run local-first: models, storage and logs stay on infrastructure you choose, and egress is a decision you make in writing.

What changes here

Same modules, Germany hours.

Data residency

Local models and storage by default; nothing leaves your perimeter without a written decision.

Compliance artefacts

Action logs, permission tiers and a kill switch a DPA conversation can use.

Overlap

09:00–13:00 CET live; the rest of the day is asynchronous.

01Germany questions

Local, and short.

Everything else is answered on the main page.

Do you work with clients in Germany?+
Yes. Engagements in Germany run on Europe/Berlin (CET/CEST) hours, 09:00–17:00 CET, Monday to Friday. Delivery is asynchronous by default with one live overlap window per day.
What does it cost in Germany?+
The teardown call is free. Audits start at USD 500 and module builds are scoped. Pricing is quoted in USD everywhere so it does not drift with exchange rates; local invoicing is available on request.
Is the module different per country?+
No. The downloadable module is identical worldwide and free. Country pages only change how the engagement is scheduled and invoiced.