> ## Documentation Index > Fetch the complete documentation index at: https://docs.nora.my/llms.txt > Use this file to discover all available pages before exploring further. # Settings > License key, host port, reset, and full uninstall — reachable from the gear icon on any setup screen. The Settings overlay is reachable from the gear icon in the top-right corner of the Landing and Dashboard screens. It's a small panel with two inputs and three action buttons. Anything you save is written to `~/.nora/onprem/.env.onprem`, and the stack restarts on save when a value has actually changed. ## Fields ### License key The paid-license activation string. When it's blank, the workspace runs in **free tier**: 1 workspace, 3 flows, and 100 daily invokes. * The value is stored as `NORA_LICENSE_KEY` inside `.env.onprem`. * The server picks it up on the next start. When you click **\[Save + Restart]** with a changed value, the app stops and starts the stack for you. * For fully offline installs, use `NORA_LICENSE_FILE` (a path to a license JSON on disk) instead. See [Air-gap tarball](/local-app/deploy/airgap) for the offline license flow. ### Host port The TCP port your Nora instance listens on. The default is `8090`. * The value is stored as `NORA_HOST_PORT` inside `.env.onprem`, and it applies to the `nora-server` container's port map. * Change it when something else on your machine is already on `8090`, or when you want to run two Nora instances side by side. * Changing the port stops and restarts the stack. The SPA and API move to the new port, and MCP links regenerate against the new `NORA_PUBLIC_URL`. ## Actions ### Save + Restart Writes the fields above into `.env.onprem`. If the stack is already running, the app runs a stop-then-start so the new values take effect immediately. ### Reset (drop data) Destructive. It drops the Postgres and Qdrant volumes — workspaces, users, flows, memory, and the retrieval index are all gone. Configuration (`.env.onprem` and `docker-compose.yml`) stays in place, so the next start boots the same shape. * The button asks you to type **`reset`** into a confirmation box before it runs. There is no undo. * Docker images stay in the daemon's image store. Only the mounted volumes are dropped. You can do exactly the same thing from the CLI: ```bash theme={null} docker compose -f ~/.nora/onprem/docker-compose.yml \ --env-file ~/.nora/onprem/.env.onprem down -v ``` ### Uninstall The full teardown. It stops every container, drops the volumes, removes the Nora-owned images, deletes `~/.nora/onprem/`, and quits the app. * The button asks you to type **`uninstall`** into a confirmation box. There is no undo. * The `.app` bundle itself stays on disk — drag it to the Trash on macOS, or use **Add or Remove Programs** on Windows, to finish. * The desktop process exits about 400 ms after the reply lands, so you see the app close on its own. Don't force-quit during that window. * The bundled `postgres`, `redis`, and `qdrant` images stay behind because other projects on the same machine may share them. Remove them with `docker image prune` if you want the disk back. ## Where the config lives Everything the app persists on the host sits under `~/.nora/onprem/`: | File | What's in it | | - | - | | `docker-compose.yml` | A copy of the compose file bundled inside the app. Overwritten on every install so app upgrades take effect; edit it if you need custom mounts or environment beyond what Settings exposes. | | `.env.onprem` | The environment used by the compose stack. Written by the Settings panel; hand-edit for anything Settings doesn't cover — SSO client ID and secret, `NORA_AIRGAP`, `NORA_PUBLIC_URL`, and so on. | Changes to either file take effect on the next stack start. The tray's **\[Restart stack]** menu is the fastest way to apply them. ## Next Check for updates online, or import an offline update tarball. Offline install and the `NORA_LICENSE_FILE` flow.