Skip to main content
FAQ

The most common questions around the current release

This FAQ answers platform, licensing, file-workbench, module-scope, and download questions directly. It does not turn roadmap ideas into promises.

Which platform is the top priority right now?
Does the app require constant connectivity or online-only licensing?
What files and transfer flows can the tool workspace handle?
Are modules fixed, or can they be packaged by tier?

Which platform is the top priority right now?

Windows is the primary target today for packaging, installation, file preview, and local file-system interaction. Other desktop platforms may run some capabilities, but the site does not present them as equally mature.

Does the app require constant connectivity or online-only licensing?

No. Module availability is determined by invitation-code configuration plus local database activation records, which fits offline licensing, LAN deployment, and weak-network usage.

What files and transfer flows can the tool workspace handle?

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.

Are modules fixed, or can they be packaged by tier?

Modules are controlled by invitation-code tiers and already work at submodule granularity. Regular tasks, recurring tasks, molds, products, customers, chat, and permission-related modules can all be toggled independently.

How does local data and session recovery behave?

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.

What is the primary download entry on the website?

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.