Renate's last day
The cake is eaten, the desk is empty, and the returns process still works, because it lives in the knowledge base with her name in the sources.
34 guides · authored 2025 to 2026
Use Cases Build a Knowledge Base
Write down what only Renate knows
Every team has a Renate: the person who knows which supplier bends deadlines, why the old price still applies, and what the error light actually means. paless gives that knowledge a home: guides and handover notes written in the editor built into paless, living next to the documents they explain, answered by Pal with sources cited.
Sound familiar?
The answer is a person
The process exists, but only as an interruption: ask the one colleague who knows. When they are on vacation, work waits. When they retire, the process retires with them.
The wiki nobody waters
There was a wiki once, in a separate tool with a separate login. It answered 2021 questions well. Nobody has updated it since, because it lives nowhere near the actual work.
Onboarding by a thousand questions
New colleagues learn by asking, which means the experienced ones teach by being interrupted. Six months later the newcomer is productive and the teacher is behind.
Knowledge base
Documentation that lives with the documents
A knowledge base fails when it is a separate place. In paless, the guide sits next to the contracts, scans and letters it explains, written in the editor built into paless, kept current where the work happens, and searchable through the same Pal that reads everything else.
An editor where the archive is
Write checklists, process guides and handover notes directly in paless, with Pal helping to draft and structure. Versioned, searchable and stored on EU servers like everything else.
The archive is half the knowledge
Thirty years of contracts, manuals and correspondence already answer more questions than any wiki. Import them, and OCR makes even the oldest scans part of the knowledge base.
Answers that cite their author
Ask Pal how something is done and the answer names its source: the clause in the supplier agreement, or the checklist a retiring colleague wrote in their last month.
Ask Pal
“How do we set up the label printer for the winter batch?”
Switch to the cold storage labels and lower the print temperature; the full sequence is in the printer guide. Karl's note adds: run two test labels first, the first one always smears.
Sources
- Printer guide · maintenance
- Handover notes · K. Steiner, 2025
The knowledge base and its editor are part of the Business plan. See what's included
Day to day
The company memory, handled
Six ways a knowledge base in paless earns its keep every week.
Guides drafted with Pal
Describe the process out of your head and let Pal structure it into a clean guide. Writing documentation stops requiring a free afternoon.
Notes next to the evidence
The returns checklist links the distributor agreement it implements. Reader and source are one click apart, so guides stay honest.
Versioned as it evolves
Processes change; guides keep up without losing their history. The current version is obvious, and last year's is still there.
Ask instead of browse
Nobody navigates a knowledge tree at 7 a.m. in the workshop. They ask Pal and get the paragraph they need, source cited.
Onboarding without interruptions
New colleagues ask Pal the thousand small questions, and the experienced ones only get the interesting interruptions.
Handover as a habit
The retiring foreman writes notes in his last months, with Pal drafting alongside. What he knows stays a company asset, not a farewell gift.
Three moments it pays for itself
Knowledge with the same protection
Guides and notes are company assets, so they get the company treatment: AES 256 encrypted, three replicas across European data centers, one isolated backup.
3 replicas · 1 isolated backup · EU
The newcomer's day three
By Wednesday the new colleague has asked Pal forty questions and a human only four. Both sides call it the best onboarding so far.
40 questions · 40 cited answers
Built for Europe
Your know how stays under European law
A knowledge base concentrates exactly what competitors would love to read. paless keeps it on isolated European infrastructure, encrypted with AES 256 at rest and TLS 1.3 in transit: no Big Tech, no US CLOUD Act. And a structured export compatible with the open source paperless-ngx project means the company memory remains portable company property.
GDPR compliant EU AI Act compliant AES 256 encryption No US CLOUD Act Redundant storage
Read the security overview Questions people ask
Which plan includes the knowledge base?
The knowledge base and the editor built into paless are part of the Business plan. Document storage, search and Pal are part of every plan.
How is this different from a wiki?
It lives where your documents live. Guides sit next to the contracts and manuals they explain, Pal answers from both at once, and there is no separate tool to keep alive.
Do we have to write everything from scratch?
No. Your archive already knows a lot: imported contracts, manuals and correspondence become askable immediately. Written guides then capture what was never on paper, with Pal helping to draft.
Can several people work on the knowledge base?
Yes. The Business plan is built for teams: colleagues read, ask and contribute according to their access, and every guide keeps its versions as it evolves.
Give the company a memory that stays.
The campaign launches on Kickstarter, with time limited Founder's Pricing for early backers.
Keep reading: All use cases Frequently asked questions