FAQ

Do I need an account to use Computtite?

Both modes require a Computtite account. Account creation is free and uses email + password. The difference is what happens after you sign in: local mode keeps all your data on your machine with no internet needed for day-to-day use; cloud mode syncs your workspace online and enables team collaboration, member invitations, and integrations.

Is Computtite really free?

Yes. Computtite is free to download and use with no feature restrictions, no usage limits on assets or employees, and no time-limited trial. It is funded voluntarily through Patreon donations under the SaaX (Software as an Experience) philosophy. A free workspace supports unlimited assets in both local and cloud modes.

Can I switch from local mode to cloud mode later?

You cannot convert a local workspace to a cloud workspace in-place, but you can create a new cloud workspace, export your local workspace as a file, and import it into the new workspace. Then recreate your team members and re-invite them. This process is manual but straightforward for most inventory sizes.

Can I have multiple workspaces at the same time?

Yes. Computtite supports multiple workspaces and you can switch between them from the workspace selector in the sidebar. Each workspace is completely isolated — its own data, its own asset types, its own members (in cloud mode). Local workspaces are unlimited.

Where exactly is my data stored?

In local mode: a single file on your machine. On Windows: %APPDATA%computtite.db. On macOS: ~/Library/Application Support/computtite.db. On Linux: ~/.config/computtite.db. You can reveal the folder from Settings → Storage → Reveal in file manager.

In cloud mode: your device keeps a local copy that allows offline operation, plus a synchronized copy stored securely online. Integration credentials are kept server-side and never in your local file.

What happens to assets when I delete an employee?

Deleting an employee automatically closes all their active assignments, returning those assets to the unassigned pool. The historical assignment records are preserved — you can still see in the asset's history that this person held the equipment. The employee may appear as "Former employee" in older history entries.

How do derived fields (days_until, years_since) work?

Derived fields are computed at display time, not stored. Every time Computtite renders an asset, it reads the source date field and calculates the derived value using the current date. This means a "Days until warranty expires" field always shows the current remaining days without any scheduled job or manual update. The source date field must have a valid value for the derived field to show a meaningful number — if the source is empty, the derived field shows blank.

Are reports real-time or snapshots?

Reports are generated from the live workspace at the moment you run them. Saved reports store the report configuration (type, filters, sort order) — not the result. Each time you run a saved report, it reflects the current state of your inventory. If you need a historical snapshot, export the report to CSV or Excel immediately after generating it.

Can I customize the column layout in reports?

Reports use the field definitions from your asset types to determine columns. The Inventory report, for example, will show all fields defined for the selected asset type as columns. To add or remove columns, modify the asset type's fields in Forge. For department, employee, and assignment reports, the columns are fixed by the report type but include all relevant data fields.

Does Computtite run on Intel Macs?

v3 officially supports Apple Silicon (M1 and newer) only. Intel Macs are not officially supported in v3, though the app may run via Rosetta 2 translation — this is untested and unsupported.

How do I report a bug or request a feature?

Open an issue on the GitHub repository. For bugs, include: your Computtite version (from Settings → About), your OS and version, a description of the expected vs. actual behavior, and steps to reproduce. For feature requests, describe the use case — not just the desired UI change, but the workflow problem you're trying to solve.