Getting Started with Unfour

Use the Download page to get the Stable package for your platform. Signing, architecture, and platform availability are documented there.

1. 1 Launch Unfour. The app opens into the desktop workbench and creates local application storage on first use.
2. 2 Choose a workspace from the title area or keep the default workspace.
3. 3 Use the module navigation to open API Client, SSH, Database, or the Workspace environment editor.
4. 4 Open Settings for appearance, account, Cloud Sync entitlement, and MCP client setup.

A workspace is the shared context for related API requests, SSH and database connections, environments, variables, activity, tabs, and MCP policy. Use separate workspaces when services or environments should not share this context.

• ✓ API collections, folders, saved requests, and request history belong to the active workspace.
• ✓ SSH and Database connection definitions are scoped to the workspace; their secret values remain local credential references.
• ✓ Workspace defaults and the active environment resolve variables such as {{base_url}} before supported tools run.
• ✓ MCP tools operate against a workspace and its environment policy rather than unrestricted global resources.

Move a project setup together instead of recreating each tool by hand: API collections, folders and requests, SSH/Database connection settings, workspace and environment variables, Saved SQL, SSH Tasks, and Flow definitions. Resource references are remapped to the imported copy.

1. 1 Select the source workspace, open its menu in the title area, and choose Export Current Workspace. Check the workspace name shown in the dialog.
2. 2 Choose Share definitions or Encrypted backup. Review Keep local paths. For a backup, enter and confirm a password of at least 12 characters; review Include saved credentials and secret variables and turn it off if you do not want them in the file.
3. 3 Choose Save Location and save the file. Inspect a sharing export before sending it to someone else. Keep an encrypted backup and its password separately.

1. 1 Open the workspace menu and choose Import Workspace from File. Select a definitions export or encrypted backup. For an encrypted file, enter its password and choose Review Import to unlock the preview locally.
2. 2 Review resource counts, the new workspace name, excluded content, and fields that need configuration. MCP access defaults to Disabled; choose a policy explicitly for this device if needed. The source workspace’s MCP policy is not imported. Previewing creates no workspace and runs no requests, scripts, SQL, or tasks.
3. 3 Expand Review and adjust local paths. Replace a path prefix or edit individual SSH private-key, SQLite, and SSH upload/download paths for this device. Choose Apply and Check Paths; review the updated preview after changes.
4. 4 Choose Create and Switch. Import creates an independent workspace with fresh resource references, adds a copy suffix for name conflicts, and leaves existing workspaces intact. It does not merge into or overwrite a workspace.
5. 5 Before running anything, fill missing credentials or redacted fields, supply referenced files separately, and select API multipart upload files again. Review SSH host trust and the imported workspace’s MCP permissions. A path check does not test remote connectivity.

• ✓ Included credentials restore only to supported local fields. SSH/Database passwords and SSH key passphrases get fresh OS credential-store references; API sensitive fields and secret variable values restore to their local SQLite fields. Encrypting the backup file does not encrypt local SQLite storage.
• ✓ Private-key files, SQLite database files, and upload/download file contents are not embedded. Histories, tabs, layouts, SSH host trust, and Cloud Sync bindings are excluded. This is a configuration backup, not a database backup or a complete device migration.
• ✓ Literal secrets in bodies, scripts, SQL, and Flow defaults remain subject to redaction, even in a backup. Arbitrary free text may still contain hardcoded sensitive information; inspect it before sharing and review redacted definitions before execution.
• ✓ Local backups are separate from Pro Cloud Sync and do not enable Secret sync or end-to-end encrypted cloud sync. Sensitive values stay excluded from Cloud Sync; Flow definitions and run history remain local-only.