Longer reads for the people who decide: data sovereignty, compliance and running open source at the scale of an organisation.
What the guides are for
The guides are the long form. They are written for the people who decide where an organisation's data and software run and then have to defend that decision: to a board, an auditor or a regulator. They explain the law and the trade-offs in enough depth to brief someone else, without assuming you run servers yourself.
Start with data sovereignty if the question in front of you is jurisdiction: what the nLPD and the GDPR require, what the US CLOUD Act can reach, and why a data centre in Switzerland is not the same thing as data under Swiss control. It ends with the questions to put to any provider, Pilae included.
The guides sit next to two shorter kinds of page. For one specific move off a SaaS, the migration guides go step by step and are written for the engineer doing the work. For a single term, the glossary defines residency, sub-processors, exit strategies and the rest in a paragraph each. And for how Pilae itself answers the jurisdiction question, the jurisdiction page in the trust centre says it plainly.
Tell us what you need to run.
Thirty minutes with an engineer, a written plan and a fixed price for the first workload.