PIM Multiuser is PIM for a household or a team. One computer runs it, and everyone signs in with their own account from a browser, a phone included. Each person’s notes, calendar, mail and documents are kept apart from everyone else’s, and the AI runs on that computer, never in someone else’s cloud.
Everyone gets the same apps as PIM Desktop: Notes, Diary, Worklog, Calendar, Author, Task, Plan, Project, Contacts, Finance, RSS, IM, Mail, Social and Documents. Just for yourself on your own computer? PIM Desktop is simpler.
What it needs
- A computer that stays on: a home server, a spare PC, a small box in the office, running Ubuntu 26.04 or later, or any other Linux with Docker or Podman. About 10 GB of memory runs PIM’s recommended AI model well; with less, it picks a smaller one.
- Internet access once, while installing: it downloads the AI (about 8 GB). After that, PIM works on your own network.
Install
PIM Multiuser is a server: it brings its own database and AI service, so it comes in two forms, not as a single program file. Pick by the Linux on the computer that will run it:
- Ubuntu 26.04 or later: the
.deb, below. One command installs everything. - Any other Linux (Debian, Fedora, openSUSE, Arch, an older Ubuntu, …): the containers, with Docker or Podman.
Ubuntu 26.04 or later: the .deb
Download pim-multiuser.deb and copy the downloaded file to that computer, open its folder in a terminal and run:
sudo apt install ./pim-multiuser_*_amd64.deb
apt may note that the download is “performed unsandboxed as root”; that’s harmless. That one command sets everything up: the database (PostgreSQL), an encrypted connection with this server’s own certificate, the AI, and the service that keeps PIM running. When it finishes, it prints the address to open.
Any other Linux: containers
Here PIM Multiuser runs in containers: the server, its database and the AI, set up the same way.
Before you start: install Docker or Podman from your distribution’s packages (or Docker’s own),
not the Docker snap, which can’t start PIM’s containers. With Docker, run the commands below with
sudo unless you’re in the docker group. With Podman, also install podman-compose and write
podman compose wherever it says docker compose.
Save
pim-multiuser-compose.yamlto a folder of its own, and open that folder in a terminal.Tell PIM this computer’s names, before the first start: the server’s certificate is made once, for exactly these names. These two lines find the computer’s name and its address on your network, write them to a file called
.env, and show it:n=$(uname -n); a=$(ip -4 route get 1.1.1.1 | sed -n 's/.* src \([0-9.]*\).*/\1/p') printf 'PIM_SERVER_NAMES=%s,%s.local,%s\n' "$n" "$n" "$a" > .env && cat .envIt shows something like
PIM_SERVER_NAMES=office-pc,office-pc.local,192.168.1.20. If people will use another name for this computer, add it at the end of that line, after a comma.Start it. The first start downloads the AI model (several GB) in the background:
docker compose -f pim-multiuser-compose.yaml up -d docker compose -f pim-multiuser-compose.yaml logs -f ai-setup # how far the download is; Ctrl+C to stop watchingShow the first administrator’s password, for the sign-in below:
docker compose -f pim-multiuser-compose.yaml exec server cat /data/first-admin-password
The address to open is one of the names from step 2, for example https://office-pc.local:8443/.
To upgrade, download the compose file again from this page (it always gets the newest)
and save it over this one, then run
docker compose -f pim-multiuser-compose.yaml up -d again; everyone’s data stays.
To change the names later, edit .env, then delete the old certificate and start again. Each PIM
Client then asks once to accept the new certificate:
docker compose -f pim-multiuser-compose.yaml run --rm --no-deps --entrypoint rm init /config/tls/keystore.p12
docker compose -f pim-multiuser-compose.yaml up -d --force-recreate
Reaching it from other computers
If this computer has a firewall turned on, other computers and phones can’t reach PIM until you open its port, 8443. Fedora and openSUSE have one on by default:
sudo firewall-cmd --permanent --add-port=8443/tcp && sudo firewall-cmd --reload
On Ubuntu and Debian the firewall is usually off; if you turned it on, run
sudo ufw allow 8443/tcp.
First sign-in
Open that address in a browser (https://<the computer's name or address>:8443/). The browser
warns about the certificate once: it’s the server’s own, and the connection is still encrypted.
Sign in as admin with the password the install made. With the .deb, show it with this (in
containers, see above):
sudo cat /var/lib/pim-multiuser/first-admin-password
The Setup page opens and asks for three things: a name for your household or team, your own password in place of that one, and the AI model, with the one that suits the computer marked. Then add the people who’ll use it on the Accounts page; everyone can change their own password on the Password page.
The PIM Client
Everyone can use PIM Multiuser from a browser. The PIM Client is the desktop program for it:
the same apps, in PIM’s own window, on each person’s computer, whatever Linux it runs. On Debian 12 or later, Ubuntu 24.04 or later, or a distribution based on
them, install the .deb (download it):
sudo apt install ./pim-client_*_amd64.deb
On any other Linux (Fedora, openSUSE, Arch, …), use the .tar.gz (download it): unpack it in a folder you own
and start it from there, no administrator needed:
mkdir -p ~/.local/opt && tar -xzf ./pim-client-*-linux-x64.tar.gz -C ~/.local/opt
~/.local/opt/pim-client/bin/pim-client
Start PIM Client and sign in with the server’s name or address (for example
kappel-pc.local), your profile and your password. Your server made its own certificate, so the
first time, the client shows that certificate’s fingerprint, a long line of letters and
numbers. Compare it with the one on the server’s Accounts page (the install printed it too) and
accept only if they match. The client then trusts exactly that server, doesn’t ask again, and warns
you if its certificate ever changes.
Upgrading keeps everyone’s data. Removing PIM Multiuser, even with apt purge, never deletes the
database: it holds everyone’s data, so the purge prints the commands to delete it yourself.
Release news
PIM changes quickly before 1.0. Leave your name and email and we’ll tell you when a new release is out (unsubscribe any time). We first send a link to confirm your address; the page it opens has all the downloads too.
PIM is in pre-1.0 testing: these builds are free to download and run. See License & Terms for what that means now, and what changes at 1.0.
Trouble installing, or questions? Email support@pim.knoden.com.