--- url: https://docs.codefox.ai/self-host/running-arctic.md --- # Running Arctic This page covers what is specific to running Arctic, the meeting notetaker, on your server: its sizes, its notetaker bots and their accounts, its sign-in, and what its backup leaves out. ## Where it runs | | | |---|---| | Folder | `/opt/recall` | | Address | `meet.` beside other apps; on its own, the whole name you give it | | On the server | `127.0.0.1:3000` | | Services | `app`, `bot-service` (one per meeting it can record at once: `bot-service-2` and so on), `stt` (speech to text), `db`, `updater`, and `caddy` when it runs on its own | | Settings | [Arctic settings](/reference/settings/arctic) | Arctic installed on its own runs its own Caddy web server on ports 80 and 443. Beside other apps it uses the shared one. An Arctic installed on its own cannot be moved behind the shared web server by the installer. ## Sizes and meetings at once Each meeting Arctic records has its own notetaker bot, a browser that joins the call. Arctic transcribes the audio on your server (the `stt` service), so nothing leaves the server for transcription. Both keep the CPUs busy for as long as a meeting runs, so give Arctic dedicated CPUs, not a burstable server type. | Size | Meetings at once | |---|---| | `baseline` | 1 | | `personal` | 2 | | `fleet` | 4 | | `fleet-8` | 8 (not yet proven) | The installer picks the largest size the server meets, up to `fleet`. To choose one yourself, run `foxden init --tier `; `fleet-8` is never picked for you. `--tier` works only when Arctic is the one app you install. The CPU, memory and disk for each are on [Server sizes](/reference/sizing). ## The notetaker accounts A notetaker joins a meeting as a guest by default, and the meeting's host may have to let it in. To join as a signed-in account instead, give Arctic its own accounts. Use accounts made for the notetaker, not a person's. 1. Open Arctic and go to **Connect the notetaker** (`/connect`). 2. Choose the account: Google (for Meet, needed when a meeting only admits signed-in accounts), Zoom (for hosts that admit only signed-in Zoom users), or Microsoft 365 (Teams joins as a member of your organisation instead of an unverified guest). 3. Type the account's email and password. The notetaker signs itself in; when the provider asks for a code or an approval on a phone, the page asks you for it. Then set `BOT_ACCOUNT_NAME` to the Google account's name as Meet shows it, so the notetaker recognises itself in the list of people in a call: `foxden config set BOT_ACCOUNT_NAME "Notetaker" --product arctic`, then `foxden restart --product arctic`. Google signs the notetaker out after a while. `foxden doctor` warns from day 10 of its sign-in and fails at day 14: sign it in again on the same page. ## Sign-in * **With Admin on the server**, people sign in to Arctic through Admin, and Admin decides who can use it. * **On its own**, Arctic has a sign-in gate in front of every page: the username `arctic` and a password the installer makes and shows once on the hand-over screen. Behind it, people sign in with Google or Microsoft when Arctic's own client is set (`AUTH_GOOGLE_ID`, `AUTH_MICROSOFT_ID`), or with an email and password; the hand-over screen prints a setup link that makes the first account. Once everyone can sign in, set `ARCTIC_BASIC_AUTH_GATE` to `off` to remove the gate. After the install, open `/onboarding` to finish setting Arctic up and check your first transcript. See [Set up Arctic for your team](/apps/arctic/set-up-for-your-team). ## Updates Arctic keeps its own **Install updates automatically** switch in its **Settings** › **Updates**, and starts with it off. An update waits, for up to 20 minutes, while meetings are being recorded, and gives up if they are still running. See [Update and restart the apps](/self-host/update). ## Its data and its backup The nightly backup at 01:35 holds Arctic's database: meetings, transcripts and calendar connections. It does not hold: * the notetaker accounts' sign-ins: connect them again after a restore on a new server; * video recordings, which the bots keep only when video recording is on. Arctic also installs a daily disk guard (at 04:17) that removes Arctic's old images and, above 75% disk use, clears more, because a full disk stops the bots recording.