Two ways to run papyro: on papyro's servers in Germany, or on the company's own ground. Pick the one the programme's IP and export rules call for, and see where each kind of data is kept and who can read it.
How papyro Cloud keeps the data
papyro serverNuremberg, Germany
at restencryptedin transitTLSbackupsEU, encryptedregionnever leaves the EU
Kept in the EUDocuments, comments, schedules and review rooms live on one server in Germany, encrypted at rest, with EU backups.
github.com/acme-space/sat-1
documents
Verification plan
Interface requirements
Interface control document
AIT plan
sync both ways
In a repository the company ownsEvery document, comment, RID and version is a file in the company's own Git repository. Clone it, read it, leave with it. It is yours.
Own API key
Own cloud account, EU region
Local LLM on own hardware
✦ LISE sends
the question the excerpts it quotes nothing else
LISE, on a model the company choosesLISE builds on a general language model, and the company picks which one. The model brings the fluency. LISE brings the ECSS/industry knowledge, the project context and the rules.
GDPRData in the EU · Art. 28 processing agreement on request · export and erasure built in
Hetzner, NurembergISO 27001-certified data centres · encrypted EU backups
How papyro runs on the company's own ground
Company serverOn the company's network
locationcompany's choiceaccesscompany onlybackupscompany's policypapyroholds no copy
Kept on the company's groundDocuments, comments, schedules and review rooms live on the company's own servers, or on a dedicated EU instance run for it alone.
git.acme-space.internal/sat-1
documents
Verification plan
Interface requirements
Interface control document
AIT plan
sync both ways
In a repository the company ownsEvery document, comment, RID and version is a file on the company's own Git server, behind its own firewall.
Own API key
Own cloud account, EU region
Local LLM on own hardware
✦ On site
questions and excerpts stay in the building
LISE, on a model the company choosesOn its own ground, the company can run LISE on a local model, so questions and excerpts never leave its network. LISE still brings the ECSS knowledge, the project context and the rules.
Self-hostedRuns inside the company's environment · no copy on papyro's servers or backups
Export controlTechnical data stays behind a boundary the company controls
Dedicated EU instanceAn isolated instance run for one company, under its own agreement