Install BluBeam on Linux.
Written for both a Linux desktop and a headless server. From system requirements to Pro activation and backups.
- 64-bit Linux: Ubuntu 22.04+ / Debian 12+ (desktop or server). Other modern distros work with the standard desktop libraries.
- CPU/RAM: 2+ cores and 4 GB RAM minimum; 8 GB recommended when running many agents.
- Disk: ~500 MB for the app + Electron runtime, plus room for backups.
- Network: outbound HTTPS to your AI provider(s) and to blubeam.pro for updates and Pro activation.
- An API key for at least one AI provider (you'll paste it into Settings after install).
- For a headless server: a desktop session or X/Wayland forwarding, since BluBeam is a desktop app (see the server note below).
- 1Download the package
Get blubeam_<version>_amd64.deb from the Download page.
- 2Install it
Run: sudo apt install ./blubeam_<version>_amd64.deb — apt pulls in the required libraries automatically.
- 3First launch
Open BluBeam from your app menu, or run blubeam. The first run fetches the Electron runtime if it isn't embedded.
- 4Add a provider key
Go to Settings → API Keys and paste your AI provider key.
- 5(Optional) Activate Pro
Settings → License → paste your Pro key → Activate. The edition badge flips from Basic to Pro and templates unlock.
- 6Set up backups
Settings → Backup / Restore — pick a location and schedule (default: daily at 12:01 a.m.).
BluBeam is a desktop application, so a server needs a way to render its window. Two common approaches are remote desktop / X-forwarding, or a virtual framebuffer for always-on scheduled jobs.
- 1Install the package
Use apt exactly as in the desktop steps.
- 2Provide a display
Use remote desktop / X-forwarding (ssh -X) or a virtual framebuffer (e.g. Xvfb) so the app can start.
- 3Keep it running
Launch it in your desktop/VNC session so the scheduler stays active for overnight jobs and weekly backups.
- 4Lock it down
Restrict inbound access to the server; BluBeam only needs outbound HTTPS.
Because BluBeam is a desktop (Electron) app, a headless server needs a display method (X-forwarding, VNC/RDP, or a virtual framebuffer). If you specifically want a pure no-GUI daemon, that's a different build — plan for a desktop session on the server for now.
- BluBeam opens and the header shows your edition (Basic or Pro).
- A test message to an agent returns a reply (provider key works).
- A scheduled test job fires at the set time.
- A manual backup writes files to your chosen location.
- Pro only: Workflow Templates are visible and the cost dashboard shows spend + retry stats.