← mttrly.com/Technical details

How mttrly works

Technical architecture and AI pipeline.

Architecture

Central service in Node.js/TypeScript with WebSocket connections. Lightweight agent process on customer servers executes SSH-constrained commands and streams structured results back. PostgreSQL for audit logs and incident history. Hosted at app.mttrly.com.

AI Pipeline

Two-model architecture. Claude Haiku handles real-time triage, intent parsing, and Telegram message formatting — optimized for sub-second response. Claude Sonnet handles multi-step incident diagnosis, log interpretation, and remediation planning — optimized for reasoning quality.

The split reduces cost and latency while maintaining quality on reasoning-intensive tasks.

Claude Haiku — Fast triage
  • → Incident classification
  • → Intent parsing from Telegram
  • → Message formatting
  • → Sub-second latency
Claude Sonnet — Deep reasoning
  • → Multi-step incident diagnosis
  • → Log interpretation (50–200 lines)
  • → Remediation planning
  • → 3–5 reasoning iterations per incident

Safety Architecture

Every design decision assumes the AI can be wrong.

Command allowlists

The AI can only suggest commands from an operator-defined allowlist per workspace. No arbitrary code execution.

Human approval flows

Restart, rollback, config changes, secret rotation — none execute without explicit Telegram approval from the workspace owner.

Audit log with reasoning chain

Every action logged with complete model input, model output, and execution result. You can see exactly why the AI recommended each step.

Escalation on uncertainty

When the model lacks sufficient context, it escalates to human review instead of attempting a low-confidence fix.

Read-only by default

Diagnostic commands run automatically. State-changing commands require approval. Enforced at architecture level, not prompt level.

In our March 2026 beta: 48 actions blocked by safety policy before reaching approval · 7 approved by human · 22 incidents resolved through read-only diagnostics alone.

Playbooks

19+ built-in validated operations:

healthcheckservice restartrollbacklog taildisk checkmemory checknginx reloadcert checkdisk cleanupport checkcontainer statusdmesg checkload checkserver discoveryand more (19+ total)