Open source · Self-host

Your fleet. Your hardware. Your platform.

Everything Plexus Cloud runs, running on machines you control — installed in one command, licensed to never phone home.

01

Overview

The entire Plexus platform — ingest gateway, ClickHouse storage, dashboards, alerts, read API — runs on your own infrastructure. One command, five questions, every secret generated locally:

curl -fsSL https://plexus.company/install.sh | bash

Free for a single team with no usage caps, and nothing phones home — license validation is offline by design, because half our users can’t reach the internet from their networks anyway. The source lives at github.com/plexus-oss/plexus.

02

Requirements

  • Docker with Compose v2, git, and OpenSSL
  • ~4 GB of RAM for the full stack
  • Linux or macOS host (anywhere Docker runs)
03

Install

The installer asks five questions — install directory, the hostname browsers will use, two optional API keys (Anthropic for the Terminal AI copilot, Resend for sign-in emails), and whether to add S3 tiered storage (default no — everything stays on local disk, no MinIO). Skip the keys and everything still works. It then clones the repo, generates every secret into a local .env (mode 600), pulls the prebuilt images, and starts the stack. First run takes a few minutes.

ServiceWhere
App — dashboards, alerts, settingshttp://localhost:3000
Telemetry ingest (WebSocket/HTTP)ws://localhost:8080
Read APIhttp://localhost:8000
04

First run

Sign in with any email address. If you skipped the Resend key, the 6-digit code prints to the server log instead of sending:

docker compose -f plexus/selfhost/docker-compose.yml logs -f frontend

The Terminal AI copilot appears once an ANTHROPIC_API_KEY is set in selfhost/.env — you bring your own key and pay Anthropic directly. Everything else works without it.

05

Day two

./selfhost/install.sh doctorstack status + health checks
./selfhost/install.sh upgradepull the next release and restart
PLEXUS_VERSION=v0.1.0pin a release in selfhost/.env

Releases are versioned tags; your install never changes until you upgrade it.

06

Free vs enterprise

Everything a single team needs is free forever — a team never hits a paywall. Enterprise features ship in the same repo and unlock with a license key set as PLEXUS_LICENSE:

CapabilityTier
Ingest, storage, dashboards, instruments, alertsFree
Single-team authFree
Grafana migration toolingFree
SSO / SAML / SCIMKey
RBAC + fine-grained permissionsKey
Audit logsKey
Multi-tenancyKey
Air-gapped release channel + CVE SLAKey

Keys are bought by email — info@plexus.company. An expired key degrades enterprise features to read-only; nothing crashes and your telemetry is never held hostage.

07

Air-gapped networks

Air-gapped deployment is a first-class target, not an afterthought. The stack makes no outbound calls except integrations you explicitly configure. License keys verify offline against a public key that ships in the source — your procurement team can decode exactly what a key grants before anything is installed. For the install itself, clone the repo and carry it plus the base images across the boundary.

08

License

The platform is source-available under the Elastic License 2.0. You can use it in production, self-host it, read and modify the code, and redistribute it. You can’t offer Plexus itself as a hosted service to third parties, circumvent the license keys, or remove the notices — that’s the whole list. The device SDKs are Apache-2.0, because code that ships inside your hardware should have no strings.