Uninstalling

What survives uninstall

Uninstalling the application removes the service registration and the application binaries only. Your data — entities/, logs/, loggers/ and the instance's licence state — is left in place on disk by design, so that a mistaken uninstall (or a planned reinstall) doesn't destroy configuration or history.

Per-platform removal

• Windows: use Add or Remove Programs, or run the MSI again and choose Uninstall. This stops and unregisters the DataOrchester service.
• macOS: quit the app, remove the launchd agent (the installer places an uninstall helper alongside the application bundle), then move the app to the Trash.
• Debian/Ubuntu: sudo apt remove data-orchester (add --purge only if you also want the package's own configuration stubs removed — this does not touch orchester.root).
• RHEL/Fedora/Rocky/AlmaLinux: sudo rpm -e data-orchester.
• Docker: docker compose down (or docker rm) removes the container; your named volumes are untouched unless you explicitly pass -v or --volumes.

Fully purging an install

If you actually want to remove all data, not just the application:

1. Confirm you have a backup if there's any chance you'll want this data later — this step is irreversible.
2. Uninstall the application as above.
3. Manually delete orchester.root (or the mounted volumes, for a Docker install).

This second step is deliberately manual and separate from the normal uninstall — removing a customer's licensed configuration should never be a side effect of a routine package removal.