Docs
Install, configure, and run PulseOps.
Back to Landing
Getting Started

Deploy PulseOps locally.

Choose a quickstart path. Docker Compose is the fastest for most setups.

Docker Compose

docker compose up --build -d
# visit http://localhost:8765

Native Go

cd cmd/pulseops

go build -o pulseops
./pulseops -config ../../config.sample.yml

Snap (Linux)

snapcraft
sudo snap install pulseops_0.2_*.snap --dangerous --classic
pulseops

First run checklist

  • Create the admin account on the setup screen.
  • Import devices or run discovery from the wizard.
  • Confirm SSH or SNMP credentials per device.
  • Enable notifications in Settings.
Requirements

Keep it simple.

Host

Linux host or VM (x86_64 or ARM). Docker or Go toolchain.

Network access

Reachable devices via SSH and/or SNMP on the local network.

Optional

SMTP credentials for outbound alerting.

Technical Notes

How PulseOps works.

  • Go backend with a lightweight web UI.
  • Metrics collected via SSH and SNMP.
  • Device inventory with JSON import/export.
  • Network scanning for local ranges and VLANs.
  • Topology mapping with saved canvases.
API highlights
GET  /api/devices
POST /api/devices/import
GET  /api/metrics/latest
GET  /api/metrics
POST /api/tasks
FAQ

Is PulseOps cloud hosted?

No. PulseOps is self-hosted so your telemetry stays local.

Can I use SNMP only?

Yes. SNMP metrics integrate with the same dashboard cards.

Is it open source?

Yes. Extend drivers, UI modules, and workflows.