This FAQ focuses on platform, licensing, the file workbench, module scope, and download facts. It does not turn future roadmap ideas into promises.
Windows is the explicit primary target today, including packaging, installation, file preview, and local file-system interaction. Other desktop platforms may run some capabilities, but the website does not present them as equally mature.
No. Module availability is determined by invitation-code configuration plus local database activation records, which fits offline licensing, LAN deployment, and weak-network usage.
It already covers local file organization, FTP / FTPS / SFTP site connection, dual-pane browsing, upload and download queues, synchronized browsing, and in-app opening for PDF, spreadsheets, Word, code, JSON, images, audio, and video.
Modules are controlled by invitation-code tiers and already work at submodule granularity. Regular tasks, recurring tasks, molds, products, customers, chat, and admin areas can all be toggled independently.
The app includes a built-in database and local state persistence. After restart it can restore recent workspaces, expanded navigation state, active sites, and part of the tool context to reduce repetitive setup.
The first website release uses the Windows installer as the main CTA, and the download page shows the current version, artifact name, latest update date, and release-note entry.