The stack
Where it runs, who can reach it, and what that means legally.
Personal data inside the EU, with a written record of where it lives and who can reach it. This site does the same: self-hosted fonts, self-hosted auth, EU hosting and no third-party scripts.
Your choice. No requirements yet? We take it from there.
- AWS
- Azure
- Vercel
- Cloudflare
- Supabase
- Docker
- GitHub Actions
What is specified, not assumed
- Region
- eu-north-1
- Rollback
- 1 click
- Alerts
- user-visible only
- Certifications
- none, said plainly
FIG. 1 · Cloud & platform
What we ship in this layer
Cloud architecture
An environment sized for what you actually run, with the bill and the failure modes explained before anything is provisioned.
CI/CD & releases
Build, test and ship on every merge, with staged rollouts and a rollback that takes one click, not one evening.
Monitoring & on-call
Alerts that fire on user-visible problems and stay quiet otherwise, because an alarm nobody trusts is worse than no alarm.
Cost optimization
Find what you are paying for and not using. Usually the largest line item is something nobody remembers switching on.
GDPR & EU data residency
Personal data kept inside the EU, with a written record of where it lives and who can reach it. Something you can show a regulator.
GDPR & EU data residency
A written record of every place personal data lands, who can reach it, and how long it stays. Something you can show a regulator, not just a marketing page.
To be clear: no SOC 2 and no ISO 27001. We would rather say so than pretend.
Usually goes with
Say what is broken. Or what is missing.
You get an estimate in hours and a ceiling back in writing, from the person who will do the work. Nothing starts and nothing is owed until you say yes.