--- url: https://docs.codefox.ai/self-host/plan.md --- # Plan your server This page helps you decide what you need before you install: the server, which apps go on it, the web address and DNS, and how Foxden lays itself out on one machine. ## The server Foxden runs on one Linux server that you own or rent. The `foxden` tool checks the server before it installs anything, and stops with the reason if the server does not fit. | Need | What Foxden expects | |---|---| | Operating system | Ubuntu or Debian. Other Linux systems (RHEL, Rocky, Alma, Fedora, Alpine, Amazon Linux) are not certified, and you install Docker on them yourself first. | | Processor | x86_64 or aarch64 (64-bit ARM). 32-bit ARM is refused. | | Access | root, or a user with passwordless sudo. When you install from your own computer, SSH with a key. | | Docker | Engine 24.0 or newer, with the Compose plugin 2.20 or newer. On Ubuntu and Debian the installer adds Docker for you when it is missing. | | Inbound ports | 22 (or your SSH port), 80 and 443. Nothing else may already listen on 80 or 443. | | Outbound | HTTPS to `ghcr.io` (the app images), `download.docker.com` (Docker, when it is missing), Let's Encrypt (certificates), and any service you connect later, such as Resend for email. | How much CPU, memory and disk depends on which apps you install. The smallest size of each app is on [Server sizes](/reference/sizing). Apps on the same server add up: three apps of 2 vCPU and 4 GB each need a server with at least 6 vCPU and 12 GB. The installer adds them up for you and marks each app in its list with whether it still fits. Two apps have more to think about: * **Arctic** joins meetings with its own notetaker bots and transcribes them on your server, so it keeps its CPUs busy for hours. Pick a server with dedicated CPUs, not a burstable type. Its size decides how many meetings it can record at once: 1, 2, 4 or 8. The installer picks the largest of 1, 2 or 4 that your server meets. Eight is used only when you install Arctic on its own and ask for it with `foxden init --tier fleet-8`, and is not validated. See [Running Arctic](/self-host/running-arctic). * **Library** stores the files of every app, so its disk grows with what your team keeps. Its size on the reference page leaves the files out. See [Running Library](/self-host/running-library). If you have no server yet, `foxden cloud` rents one in your own Hetzner Cloud account, sized for the apps you name, and connects to it. Hetzner bills you directly. ## Which apps to install You can install any mix of Fennec, Arctic, Corsac, Pampas, Culpeo, Cape and Library, and add more later. Foxden Admin is the console where you manage people, sign-in, the company and the server. When you pick two or more apps, the installer adds Admin for you. When you pick one app on a terminal, it adds Admin beside it too, except for Arctic, which can run on its own. A script that names one app gets only that app. With Admin connected, your people sign in once and reach every app they can use, and you manage the server from Admin's **Server** pages. An app runs on its own only when you install it without Admin. It then has its own sign-in and its own people. ## The web address and DNS Every app gets its own name under one domain that you own. For `example.com`: | App | Address | |---|---| | Foxden Admin | `admin.example.com` | | Fennec | `crm.example.com` | | Arctic (with other apps) | `meet.example.com` | | Corsac | `sign.example.com` | | Pampas | `forms.example.com` | | Culpeo | `agent.example.com` | | Cape | `calls.example.com` | | Library | `library.example.com` | One DNS record covers them all: an `A` record for `*.example.com` that points at your server's public IP address. Make it before you install. The installer checks it, shows you the exact record when it is missing, and can wait for it to go live. Arctic installed on its own is the exception: it takes the whole name you give it, for example `meet.example.com`, and that one name needs an `A` record. Certificates come from Let's Encrypt the first time each address is opened. For that, ports 80 and 443 must be reachable from the internet. A cloud provider's own firewall in front of the server blocks this without saying so; open both ports there too. You can move every app to another domain later. See [Change server settings](/self-host/configure). ## How it sits on one server ``` your computer the server foxden --- SSH ---> ports 80/443: one Caddy web server, one name per app |-> 127.0.0.1: each app in /opt/: app, database, updater /etc/foxden: shared settings, the box key, backup passphrases cron: one backup per app each night, one restore test each week ``` * Each app is a Docker Compose stack in its own folder: Admin in `/opt/codefox-auth`, Fennec in `/opt/codefox-crm`, Arctic in `/opt/recall`, Corsac in `/opt/corsac`, Pampas in `/opt/pampas`, Culpeo in `/opt/communications`, Cape in `/opt/cape` and Library in `/opt/library`. Each folder holds the app's compose file, its `.env` settings file, its backup scripts and its `backups` folder. * Each app has its own Postgres database and its own update helper (the updater), inside its own stack. * The apps listen only on the server itself (`127.0.0.1`). One Caddy web server in `/opt/foxden/ingress` holds ports 80 and 443 and passes each address to its app. Arctic on its own runs its own Caddy instead. * Settings the apps share (the domain, the Google and Microsoft clients, the email key and sender, the AI key, the company name and the registry login) are kept once in `/etc/foxden/suite.env` and copied into each app that uses them. * The box key in `/etc/foxden/box.key` is the one secret from which the links between apps are made. See [Keys, secrets and access](/self-host/secure). The installer also needs these ports free on `127.0.0.1`, one or two per app: Admin 3020, Fennec 3010 and 3011, Arctic 3000 and 6080 (with other apps), Corsac 3400, Pampas 3410, Culpeo 3024, Cape 3430, Library 3480 and 3481. ## Next [Install Foxden](/self-host/install).