System requirements

Everything aftercalls needs on your machine and in your browser to work. If something on this page doesn't match what you've got, reach out — we'll help you sort it.

Web portal

The portal at app.aftercalls.io runs in any modern browser — it's a single-page app, so recent evergreen versions give you the smoothest ride:

Chrome, Edge, or any Chromium-based browser version 118 or newer
Firefox version 121 or newer
Safari version 17 or newer

Also required:

JavaScript enabled. The portal renders client-side; with scripts blocked, nothing paints.
Cookies enabled for app.aftercalls.io. Your session refresh token rides in an HTTP-only cookie; if cookies are blocked the sign-in page loops.
Internet connection. Recording, transcription, summarization, and note-sync all run server-side — there's no offline mode.

Desktop app — Linux

x86_64 Linux on a modern distribution: Debian 11, Ubuntu 22.04, Fedora 36, RHEL 9, or anything newer with glibc 2.31+.

All packages

libgtk-3 runtime
libwebkit2gtk-4.1 — bundled or pulled in by package deps depending on installer type (see below)

AppImage

Requires libwebkit2gtk-4.1 on the host. The AppImage bundles everything else and updates in place when you click the Install banner.

.deb (Debian, Ubuntu, Pop!_OS)

Install with sudo apt install ./aftercalls_*.deb. Package deps pull libwebkit2gtk-4.1 automatically.

.rpm (Fedora, RHEL)

Install with sudo dnf install ./aftercalls-*.rpm. Package deps pull webkit2gtk4.1 automatically.

Desktop app — Windows

Windows 10 version 1809 (build 17763) or newer, or any Windows 11. x86_64 only — no ARM build yet.
WebView2 runtime — preinstalled on Windows 11 and on current Windows 10 via the Evergreen Bootstrapper. If your machine is missing it, our .msi or .exe installer will prompt to install it on first run.

Desktop app — macOS

Not available yet. The desktop app currently ships for Windows and Linux only, and there is no macOS installer to download.

The web portal works normally on a Mac — Safari, Chrome, or Firefox, same as any other machine. You can review, search, and share calls there. Recording is the part that needs the desktop app, so a Mac cannot capture calls today.

Common to everything

Internet connection. Recording, transcription, summarization, and note-writing all happen server-side. A momentary drop is survivable — the desktop agent buffers locally and resumes on reconnect. A sustained disconnect means nothing processes until you're back online.
Microphone access. The desktop app needs OS-level permission to record. First run prompts for it.
Disk space. Around 500 MB for the desktop install plus a working buffer for in-flight recordings. Uploads start as soon as a call ends; the local buffer clears within a minute or two of upload completion under normal conditions.