Uninstalling
Run the installer and choose Uninstall instead on the first screen. It links your account and hub workspace the same way an install does, then shows you exactly what it found deployed and removes what you leave checked.
Installer, “Before you start” panel with the “Uninstall instead” button highlighted.
What it removes
The checklist is built from what the uninstaller actually finds in your workspace, so it never offers to delete something that is not there.
| Item | Notes |
|---|---|
The lakemine-scan job | The scheduled scan. |
| The dashboard “Databricks Cost Optimization” | Removed along with its published snapshot. |
The uploaded engine under /Workspace/Applications/lakemine | Including the compiled wheel. |
| The results schema and its data | Confirmed separately. See below. |
The lakemine secret scope | The subscription key and metering credential. |
The lakemine-scan service principal | Which takes every grant it held with it. |
The lakemine-viewers group | Only if the installer created it. |
The lakemine-wh SQL warehouse | Only if the installer created it. |
| Your install slot at Lakemine | Frees the seat on your subscription. |
| Cached sign-ins on your own machine | The local Databricks CLI profiles the installer used. |
Deleting the results schema is confirmed separately, with its own checkbox, because it permanently deletes all of your findings data. Everything else is recreated by a re-install. Your history is not.
Installer, “Remove Lakemine from this workspace” panel. The checklist populated from a real deployment, with the separate “I understand the results schema and all its findings data are permanently deleted” confirmation checkbox visible.
What is never touched
Your own catalogs, warehouses, and groups.
If you pointed the install at your own catalog, only the results schema inside it is dropped. If you picked one of your own SQL warehouses, it is left running. If you chose an existing group as the dashboard viewers group, it is left exactly as it was, membership included.
The uninstaller only removes things it created.
Deleting the service principal revokes everything
The lakemine-scan service principal holds every grant the appliance was given: the
read-only access to system.*, the access to your results catalog, and the access to the
SQL warehouse.
Deleting the identity takes all of them with it. There is no separate revocation step, and no grant left behind pointing at something that no longer exists.
If something cannot be removed
Anything you lack the rights to delete is reported with the exact command to run by hand.
Re-running the uninstall is safe. It re-scans, shows what is still present, and removes what it can.
Installer, uninstall panel mid-run, log showing completed removals and one item that needs a manual command, with that command visible.
What Lakemine keeps
Nothing about your Databricks estate.
The aggregated metering already reported for past scans remains on your billing record, because it is what your invoices were calculated from. It contains counts and totals only, with no resource names, no query text, and no user identities. The full field list is in What is Lakemine.
Your Lakemine account itself is unaffected. Uninstalling removes a deployment, not your account or your subscription.
Uninstalling one install out of several
Each deployment has its own install_id, and removing one stops that deployment and
leaves your others running. The subscription check is per install, not per account.
Check which installs you have at app.lakemine.ai before you start, so you remove the one you intend to.
Lakemine portal at app.lakemine.ai, Installs page, showing several installs with their status and last check-in.
Re-installing later
Nothing carries over except your Lakemine account. A fresh install creates a new
install_id, a new service principal grant set, and a new results schema, and starts
collecting findings from its first scan.