Infrastructure & DevOps
RMM for people who read the API docs before the marketing page.
Full REST API, event-driven automation, and Linux support that actually works.
Level fits beside your stack, not on top of it. It is the operational control plane for servers and endpoints, not a replacement for observability or CI/CD.
Servers drift. Access sprawls. Alerts pile up. The work that keeps fleets healthy is the work no tool wants to own.
Configuration drifts over time
Hand-fixed servers and skipped package updates slowly pull every box away from the baseline you set.
Access is scattered
SSH keys, jump boxes, and shared logins accrete across environments with no single place to govern them.
Alerts without action
Monitoring tells you something broke, then leaves the actual fix sitting in your lap at 2 a.m.
Built for engineers, not their managers. Nothing is hidden behind a UI you can't automate.
Full REST API
Every action in the UI is available via the API: device management, automation execution, alert querying, and script runs. Webhooks push events out, and scoped API keys keep access tight.
- Every UI action available via API
- Device management, automation execution, alert querying, script runs
- Webhook support and scoped API keys
Linux depth, not a footnote
Debian, Ubuntu, Arch, Fedora, Manjaro, and Mint run the same agent on the same platform. Remote control, background management, scripting, monitoring, and patching all work, exactly as they do on Windows and macOS.
- Debian, Ubuntu, Arch, Fedora, Manjaro, Mint
- Same agent and platform as Windows and macOS
- Remote control, background management, scripting, monitoring, patching: not limited support
Event-driven automation
Pipelines trigger on device events, tag changes, alert conditions, or schedules. Chain scripts, notifications, restarts, and group changes, and use one script's output as the next step's condition.
- Triggered by device events, tag changes, alert conditions, or schedules
- Chain scripts, notifications, restarts, and group changes
- Script output usable as the next step's condition
Observable execution
Every automation run, script, and remote session is logged with full context. Watch output in real time, drill into per-device logs for fleet-wide operations, and get failure alerts with the stack context to act on them.
- Every run, script, and session logged with full context
- Real-time output, per-device logs for fleet-wide ops
- Failure alerts with stack context
“Finally, an RMM that doesn't feel like it was designed in 2005. The UI is clean, the API is real, and patching actually works reliably.”
cloudops_mike
r/sysadmin
The questions engineers ask first. Where Level fits, what it runs on, and what it logs.
Does this replace my observability stack?
No. Level is an operational control plane for endpoints and servers. It complements observability, CI/CD, and infrastructure-as-code rather than replacing them.
How does agent deployment work?
A single agent installs via script across Linux, Windows, and macOS. Enroll servers by environment and group them with tags.
Which Linux distributions are supported?
Debian, Ubuntu, Arch, Fedora, Manjaro, and Mint run the same agent and the same features as Windows and macOS.
Are automations safe to run at scale?
You target them by environment, group, or tag, gate them behind approval, and review a full per-device log of every run.
What gets logged?
Every automation run, script, and remote session is recorded with full context, with real-time output and per-device logs for fleet-wide operations.
Does Level work for on-prem and cloud servers?
Yes, anywhere the agent runs. Level manages the servers and endpoints themselves, not the cloud control plane.
Start with the docs.
The API reference and full docs are public. Start there, then bring your own infrastructure. First 10 devices free.