What is open, and what is not

Why not open source

The usual reason to publish source is so somebody can check the claims. For this product the claims are checkable without it, and more conclusively: lsof shows the program holds no network connections, and your identity is a plain SQLite file any tool can open. Source code tells you what should happen; those tell you what is happening.

The honest other half: the distillation logic is the product, and giving it away before there is anything else here would be giving away the only thing there is. That may change — opening later is easy, and closing again would not be.

What is public

Releases, the usage documentation and the issue tracker, in one repository. Every build published there is signed and notarised, and nothing is triaged in private.

What you may do

• Use it, for anything

  Personal or commercial, no seat count, nothing to register.

• Copy the app to your own machines

  As many as you own.

• Read your own data with anything

  The identity is a SQLite file. No format lock-in, no export button needed.

• Not redistribute a modified build

  The signed build is the one Apple notarised; a re-signed copy is a different product wearing this one's name.

Third-party work

The website draws its scene with three.js (MIT). The viewer uses no third-party frameworks. The engine’s dependencies and their licences ship with the app and are listed in the repository.