Skip to content
plugboard.appRequest a demo

Install it yourself

Self-hosting overview

The native release workflow currently targets Linux x64 (Intel/AMD). When a compatible package is available, it brings its own database and application runtime. Check the download centre before planning an install: configured targets and source-built launcher support do not guarantee published assets. Windows, macOS and Linux ARM native release targets are disabled.

  • A systemd service on the native Linux package that starts at boot and comes back after a crash. Windows Service and LaunchDaemon instructions cover separately built reference deployments only.
  • An embedded PostgreSQL inside the install directory, so backing up the folder backs up the instance.
  • A status panel at localhost:9090 for setup, health, updates and logs, so most care never needs a terminal.
  • Overnight updates, on by default and switchable off.

Plugboard is not demanding. The dominant cost is the database, and school-sized data is small.

School sizeSuggested
Up to 1,000 devices2 vCPU, 4 GB RAM, 40 GB disk
1,000 to 5,000 devices4 vCPU, 8 GB RAM, 100 GB disk
Above 5,000 devices4 to 8 vCPU, 16 GB RAM, 200 GB or more

Size a separately configured local AI model for its own requirements. The native bundle does not include a model; container deployments can use the model sidecar.

Disk grows with the audit log more than anything else, and its retention is configurable.

Running it yourself means owning five things.

  1. The certificate, and its renewal. See HTTPS and certificates.
  2. Backups, and having restored one. See backups and restore.
  3. SECRETS_MASTER_KEY, kept somewhere other than the server. See secrets and keys.
  4. Deciding when to update, though the default is that it handles this overnight. See updating.
  5. Noticing when it is down before your users tell you. See keeping an eye on it.
You host itWe host it
Installing and updatingYours, mostly automaticOurs
The certificateYoursOurs
BackupsYours to take off the machineTaken and tested for you
SECRETS_MASTER_KEYYours aloneHeld per deployment and escrowed
Systems on your networkReached directlyReached through a connector agent
Vendor-hosted AIUse a configured local model or your own external-provider keyIncluded, set up at first boot

See choosing a deployment if you have not decided yet.

What you need, then installing it.