The instance below runs Filum's current code, built with the same recipe as the image delivered to customers — currently ahead of the last delivered archive (1.2.1), which version 1.3.0 will catch up with. It is filled with an entirely fictional design file — a surgical drill and a diagnostic instrument — taken through the real lifecycle: released documents, opened revisions, frozen content, signatures bound to the fingerprint of what they attest, chained audit trail. Nothing in it was fabricated for the demonstration.
No sign-up, no form, no tracking.
Password shared by all 4 accounts: Demo!Filum2026. They open nothing but this instance.
| Identifier | Role | What it lets you see |
|---|---|---|
| KGA | Administrator | settings, users, archive, legal hold — and the deletion refusal |
| HVA | Approver | can sign an approval |
| NCO | Approver | quality — audit trail review, and a reading to acknowledge |
| TBR | Approver | systems engineering |
Everything entered is visible to other visitors, and erased at the next reset. For a medical device design file, both are serious. The file on display is entirely fictional — product, people, values, suppliers. One exception, and it is visible: the administrator account bears the publisher's name, so that is the name that will be printed on whatever you sign there.
Nothing signed there has any value: everyone signs in under everyone's name. A real installation is single-organisation, behind your infrastructure, with your accounts and your passwords.
The instance returns to its original state at a fixed interval. That is also what repairs it: if a visitor has changed a password, the next reset reopens the door. An account locked by failed attempts reopens on its own after a few minutes — the lock is time-based, not permanent. The application displays the reset period on every screen.
Filum runs on YOUR language-model key, never ours. On an instance with published credentials, a key placed there would be an open bill to whoever finds it. The assistant is therefore switched off in the settings and has no key — both, not one or the other: removing the key while leaving the switch on would have made the screen say the opposite of this sentence. The seed check refuses to produce a demonstration where it is enabled.
Open a released document and look at its signatures: each carries the fingerprint of the content it attests, and that fingerprint survives the next revision. Then open the audit trail: the chain is verified on screen, entry by entry. Then, signed in as KGA — deletion is reserved to the administrator —, try to delete a released document: the refusal is explicit and points you to the compliant route, a new revision.
Finally, one gesture you can perform yourself: sign in as NCO and open PLN-3010. It is distributed to you and you have not read it yet — acknowledge receipt. The list goes from two to three, your name is frozen into the record, and the audit trail logs it. Then release a revision of the document: your reading will not follow it.