Desktop setup and modes

Install the DataMaker desktop distribution provided for your organization and platform. On first launch, choose a workspace mode. Use Settings → Mode when you need to change that choice.

Solo mode

Solo mode keeps the workspace database and blob files on your machine and starts the local services needed for execution. Configure the AI connection in Settings for this installation.

Use solo mode for a personal workspace or workflows that need local execution. It does not imply offline AI: a configured remote provider still receives AI requests, and scripts can contact configured systems.

Team mode

Team mode connects to a central DataMaker API and signs in to the corresponding authentication service. Use the server URL supplied by your administrator. You can paste the address you normally open in your browser, including a page path, or the API address. A hostname without a scheme uses HTTPS. Shared metadata stays on the central service while desktop execution uses the local execution service and runner where supported.

The central service supplies AI configuration for team mode. A successful login does not prove your machine can reach a target database or API; test the relevant connection from the execution path you will use.

Change the team server

1. Open Settings → Mode and select Team. You can also choose DataMaker → Change Server… on macOS or press Alt and choose Help → Change Server… on Windows.
2. Paste the DataMaker address and select Check. The result shows the API server and its version. Check that this is the server you intended to use.
3. Select Apply in Settings or Connect in the native prompt. Changing the server restarts the desktop app and asks you to sign in to the new server. Your previous server session is cleared.

If you edit the address after checking it, check the new address before connecting. The desktop refuses a server that cannot be reached, does not identify itself as DataMaker, or requires an incompatible desktop version.

If the saved server is unavailable at startup, select Change server… in the connection dialog to enter another address. You can also retry the current server or switch to local mode.

Switching and compatibility

Changing modes selects a different workspace/backend. It does not merge local data into the central project. Export and review portable assets through the Hub when appropriate, then configure target-specific bindings again.

If the app reports a server compatibility problem, align the desktop and server releases before trying to execute. Keep existing local data until you have verified the new workspace contains everything you need.

Troubleshooting

If startup fails, inspect the app's diagnostic information and service status. Report the app version, mode, server host and failing service to your administrator, without sharing credentials or raw data. For a connection failure, separate local network reachability from authentication and workspace permissions. A proxy authentication message means you must sign in to your network proxy. A certificate verification message means your administrator should check the server certificate or your organization's trusted root certificates. If an address answers but is not identified as DataMaker, confirm the address with your administrator.

Back up local workspace data and per-install secrets together using your organization's device backup process. Do not delete application data as a routine troubleshooting step.