| FMRS | 65 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 17 / 20 | 18 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Developers and DevOps teams looking to manage self-hosted infrastructure via CLI or AI agents
- Users who want to streamline server provisioning and hardening across multiple cloud providers
- Teams that want to integrate security audits into CI/CD pipelines
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| Not for | - People without SSH access or who do not need cloud provider integrations
- Users who require a GUI or managed service rather than a CLI
- Those who need macOS/BSD support (Linux only platform)
- Those who need full Windows native support (manages Linux servers only via SSH)
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| Required permissions | - Requires access to cloud provider API tokens (Hetzner, DigitalOcean, Vultr, Linode)
- Requires SSH access to target servers to perform audits, hardening, and maintenance
- Can create SSH keys and configuration files on the local machine
- Can execute destructive operations on servers (if enabled)
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| Risks and side effects | - Destructive operations (destroy, restore, snapshot-delete, provision, restart, maintain, snapshot-create) are blocked in default safe mode; if enabled, risk of data loss
- API tokens are sensitive; ensure they are stored securely
- SSH connections may be intercepted; use strict host key verification
- Automated operations may inadvertently change server configurations
- Misuse could lead to service disruption or security vulnerabilities
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | Claude Code, Cursor, Windsurf | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 14 | 0 |
|---|