papyro turns ECSS standards into structured, reviewable documents — with Git versioning, AI assistance, and automated PDF and wiki builds.
In every space project, documentation peaks coincide exactly with the hardest engineering phases. Review gates — SRR, PDR, CDR — demand complete deliverable packages precisely when your team is deep in design crises, firefighting, and qualification campaigns.
Workload composition across a typical ECSS project lifecycle. Documentation pressure compounds at every review gate — when team capacity is already exhausted.
280+ DRDs from the ECSS catalogue with expected sections, compliance fields, and frontmatter pre-filled. Start any deliverable in seconds.
LISE is grounded in authoritative space-engineering knowledge — not generic text. Every answer stays traceable to its sources, so you can see where it comes from and verify what matters.
Documents live in your own GitLab or GitHub repository. Every change is a commit. Full review workflow with merge requests and diffs.
One click to build a Sphinx HTML wiki or xelatex PDFs — formatted to ESA house style, ready for formal review submission.
LISE doesn't generate generic text. Every answer is anchored in authoritative space-engineering knowledge and stays traceable to its sources, so your team can verify what matters.
Engineering, management, and product-assurance branches, with 280+ DRDs catalogued and cross-referenced — the distilled consensus of ESA working groups and review boards.
Answers are anchored in authoritative space-engineering knowledge rather than invented — so what LISE writes holds up to review.
Every answer points back to where it came from, so your engineers can check it and trust it — rather than taking it on faith.
LISE handles everything the standard already knows — structure, compliance language, DRD templates, frontmatter. The work that actually requires engineering judgement stays with your team.
Your documents live in your own Git repository.
EU-hosted and encrypted at rest.
Plans for teams of every size — from a single-document free tier to fully in-house deployments. See plans →
Questions about ECSS coverage, plans, or an in-house deployment? Send us a note and we'll get back to you.