# Levirge DevOps

Manage and monitor applications and systems behind firewalls. A small client,
devops-client, runs next to each system and connects outward through a message
bus, so the system needs no inbound port or VPN. People use it through a web UI,
machines through an API, and AI agents through MCP.

**Status: private testing.** devops-client has no public download yet.

## Plugins

| Plugin | Group | What it does |
| --- | --- | --- |
| [SQLite](/devops/plugins/sqlite.md) | Database | Connection, queries, saved queries, query history and audit log |
| [PostgreSQL](/devops/plugins/postgresql.md) | Database | Queries, schema browsing, resizable result columns and export |
| [MySQL / MariaDB](/devops/plugins/mysql.md) | Database | Queries, schema browsing, resizable result columns and export |
| [Redis / Valkey](/devops/plugins/redis.md) | Database | Dashboard, console, key browser and value editing |
| [MongoDB](/devops/plugins/mongodb.md) | Database | Find, aggregate and schema browsing |
| [InfluxDB 2.x](/devops/plugins/influxdb.md) | Database | Flux queries with a results table and export |
| [Log files](/devops/plugins/logs.md) | Logs | Live tail, search and read log files and whole log directories |
| [Files](/devops/plugins/files.md) | Files | Read-only file browser, confined to the folders you choose |
| [Docker](/devops/plugins/docker.md) | Containers | Read-only dashboard, gauges and containers view, with host CPU and memory |
| [MQTT](/devops/plugins/mqtt.md) | Message bus | Browse and subscribe to topics, and see broker stats |
| [NATS](/devops/plugins/nats.md) | Message bus | Server, stream, consumer and key-value monitoring, with message rates |
| [llama.cpp](/devops/plugins/llama.md) | Model server | Loaded model, live token rates and slot use |
| [Host metrics](/devops/plugins/hosts.md) | System | CPU, memory, load, network, disks, GPUs and top processes |
| [TP-Link Omada](/devops/plugins/omada.md) | Network | Sites, gateways, switches, access points, clients and alerts |

In the web UI, services are grouped in the sidebar, and you can pin the ones
you use most and switch between All and Pinned.

## For AI agents

Let agents monitor and investigate, faster. An incident spans systems: a slow
query, an error in the logs, a container out of memory. Over MCP, an agent
checks each of them in one session and comes back with the evidence.

- **One session across every system.** Databases, logs, containers, model
  servers and the message bus through one MCP connection.
- **Finds the right connection.** `find_connection` turns a name into the
  connection to use, with close matches when there's no exact one.
- **Ready-made investigations.** Prompts for a service investigation, a query
  plan, slow queries in the logs, a container health check and Redis memory.
- **Errors that say what to do next.** A failed call returns a code and, where
  there is one, the next tool to call.
- **Read-only unless you say otherwise.** Agent tokens read what they're
  granted; writes need a writer role.
- **Every agent action on record.** The audit log marks what an agent did apart
  from what a person did.

Each plugin page lists its MCP tools. More:
[How agents monitor your infrastructure](/devops/ai-agent-infrastructure-monitoring.md).
[Monitoring remote and factory sites](/devops/iot-edge-monitoring.md).

## How devops-client behaves

- **No inbound port or VPN.** devops-client connects outward through a message bus.
- **Credentials stay on the host.** Passwords, connection strings, hosts and
  file paths aren't sent over the message bus.
- **Writes need a role.** At devops-client, a caller with no role is read-only, and
  a connection can also be set read-only. These are two separate checks.
  Database writes in the web UI also ask for an authenticator code.
- **Actions are audited.** Each request is recorded in an audit log.
- **One small binary.** About 42 MB, statically linked for Linux. Windows isn't
  a target.

## Waitlist

[Join the waitlist](/devops#cta) for one email when devops-client is ready
to install.
