The company pays per project, one to two percent of the contract it runs, billed a year at a time. Everyone on the team joins at no seat fee, and the documents stay in the company's own Git repository.
Free
One plan, no clock
€0one projectfor as long as you like
Set up a real project, see its whole deliverable structure, and write one plan to a finished PDF.
1 project, its full document structure and schedule
The Risk Management Plan (ECSS-M-ST-80C) written, reviewed and built to PDF and wiki
Members join by company domain, no seat fee; reviewers free
LISE on the company's own AI account · hosted in the EU
In our survey of 24 engineers on ECSS projects, documentation took about 30% of an engineer's time on average: around a quarter in design engineering, 40% in systems engineering, 60% in product assurance and AIT. A loaded engineering hour in Munich costs €70 to €100.
From the survey:
The team spends, each year
A 15% saving, each yearpapyro, Project tier, each yearThe saving pays for papyro
1,600 productive hours a year per person. The tier follows the contract value typed above. The saving is yours to judge: 15% is one afternoon a week for someone who writes documents half the time.
Prices are per project and per year, net of VAT, quoted for the contract's duration and billed a year at a time. Extra seat €1,200 a year · a further standards pack €3,000 a year · a second project running at the same time −20%, a third −30% · a paid three-month pilot at €1,500, credited when the company moves to a plan. While papyro is in early access, plans open by invitation: talk to us.
Where the documents live.
papyro Cloud runs on servers in Nuremberg, with encrypted backups kept in the EU. Programme and Company can run on a dedicated EU instance, or on the company's own ground where no document ever reaches papyro. One page shows, for each way, where every kind of data is kept and who can read it.