Four delivery surfaces · one product
Use FileNyani where your folders live.
Hosted Web, Windows Desktop, CLI, and Docker share the same product core and portable .filenyani workspace state. Choose by environment—not by feature mode.
.filenyani
Conversations, citations, extraction artifacts, reviews, saved field lists, and rebuildable indexes stay with the folder.
Model caches, application recents, runtimes, and engine binaries stay outside the workspace.
Edition matrix
Same workflow, different host.
All editions preserve source authority, bounded evidence, explicit model preparation, and the same workspace schemas.
| Edition | Best for | Filesystem and inference | Current boundary |
|---|---|---|---|
| Hosted Web | Trying FileNyani in a current desktop Chrome or Edge browser. | File System Access plus local WebGPU inference. | Optional Browser Hybrid; app assets and models require initial network acquisition. |
| Windows Desktop | Native Windows folders with a packaged local runtime. | Native filesystem and CPU llama.cpp through a loopback-only sidecar. | Windows x86_64 release candidate; Native retrieval is lexical. |
| CLI | Developers and local terminal-driven folder work. | filenyani <folder> serves the shared UI and Native runtime on loopback. | Local package artifact; no public registry publication yet. |
| Docker | A self-hosted, bind-mounted local workspace. | Linux/amd64 container, CPU llama.cpp, separate model volume. | Bind host publishing to 127.0.0.1; no registry publication yet. |
The workspace format stays folder-owned. Desktop, CLI, and Docker emit no product analytics. Hosted Web records sanitized anonymous page views only; it does not receive workspace content, questions, answers, or product actions.
Start with the edition that fits today.
A workspace created by one edition remains an ordinary portable folder. Public packaging and distribution channels are still release decisions; the Hosted Web application is available here.