PocketOps: your fleet, one thumb away

PocketOps

SSH from a beach towel is not an incident process.

The 2am ritual is broken.Phone hotspot, a flaky VPN, a terminal at 9px, and one fat-fingered command away from a longer outage. PocketOps turns the whole ritual into a chat.
Runbooks rot in wikis.Here they execute themselves: diagnose, plan, run, verify. And the agent stops to ask before it touches anything risky.
Dashboards only watch.An operator acts. Every fix ships with logs, health checks and a receipt you can audit on Monday.

Try it: tap a scenario inside the phone.

21:4782

PocketOpsfleet: yefrix-home · 3 nodes

Evening. I am Ops, your operator for the yefrix-home fleet. All 3 nodes report healthy as of 21:47. What are we fixing tonight?

Try a scenario

Server details

node-1apps + db

Hardware: Ryzen 7 5700U · 32 GB
Address: 10.0.40.10
Uptime: 41 days 6 h
Docker: 27.5.1

node-2canary + CI runners

Hardware: Intel N100 · 16 GB
Address: 10.0.40.11
Uptime: 12 days 14 h
Docker: 27.5.1

backup-pisnapshots + offsite

Hardware: Raspberry Pi 4 · 8 GB
Address: 10.0.40.20
Uptime: 97 days 2 h
Restic: 0.17.3

Last snapshot 03:00 CEST · next tonight 03:00 · restic to backup-pi

⚡ YefrixLab demos

💰LedgerFlowFinance 🧾TaxonautAccounting ▲AI GatewayLLM ops 🗂VaultBoxFiles 📚AtlasWikiWiki 🏙FlatScoutReal estate 📱PocketOpsAI ops 🏠HabitatSmart home

↩ This case study All work →