Ask plain-language questions about the entire PEP fleet and get answers from live data — at console.marlo.run. Read-only: Marlo reports on the fleet, it never touches a mixer.
Internal — AudioLink only
The console exposes fleet operational data (church names, usage, error logs). It's behind a shared password — don't share the password or the answers outside AudioLink.
Go to https://console.marlo.run.
Enter the shared password (ask Ron). That's it — then just type your question.
A chat console backed by Claude connected to the fleet's read-only monitor. You ask in plain English; Marlo pulls the real numbers and answers, showing each data lookup it ran. It answers fleet questions without digging through routes.json or logs.
Fleet health, inventory, usage & adoption, failures, capability gaps, and per-church history — all read-only. Full list with examples: What you can ask Marlo.
Tip: name a church and give a time window ("last 7 days," "this month") for sharper answers.
It's read-only. Marlo never changes a mixer — no faders, no mutes, nothing live. It only reports.
No restart / deploy / "push latest." Those aren't built (the monitor is read-only); they'd need new tools.
It answers from the fleet monitor's data — fleet status, channel names, and the interaction log. Anything outside that, it can't see.
Marlo is a convenience layer. The fleet data comes from a read-only MCP server you can add to your own Claude (Claude Code / Desktop) and query directly — same tools, same answers. See Connect to the fleet MCP.
Password resets, something looks wrong, or you want a new kind of question answered → Ron.