mttrly for Indie Hackers
Manage all your projects from one chat
Running 5 side projects on 3 different servers? mttrly puts them all in your pocket.
🚀 Saturday Night: Site Down, You're at a Party
4 projects on 3 servers. Uptime Robot alert. Need to fix from phone.
Old way:
1. Leave party
2. Find laptop + WiFi
3. VPN (if needed)
4. SSH into server
5. Diagnose for 10-15 min
6. Fix
7. Verify
Total: 20+ minutesmttrly way:
1. Pull out phone (5 sec)
2. /status all (10 sec)
3. Ask why (12 sec)
4. Confirm fix (5 sec)
5. Done (15 sec)
Total: 47 secondsThe Problem
- ✗Too many servers to keep track of
- ✗Incidents happen during family time
- ✗SSH keys scattered across devices
- ✗Wasting time on routine maintenance
The Solution
One chat bot for all your servers. Check status, restart services, deploy updates — all without touching a laptop.
The Indie Hacker Reality
You're a one-person company. You code, you market, you do support. You don't have a DevOps team — you ARE the DevOps team. Every minute spent on server maintenance is a minute not spent on features or growth.
Multi-Server Chaos
First, there was one VPS for your main project. Then a separate one for the blog. A third for that API service. Now you're juggling DigitalOcean, Hetzner, and AWS. Each with different SSH keys, different deployments, different problems.
How mttrly Simplifies Everything
Unified dashboard
/status all shows every server's health in one message. Red flags are instantly visible.
Named servers
Use friendly names: "blog", "api", "main-app" instead of IP addresses. /restart blog is all you need.
Quick deploys
Pushed a fix from your phone? /deploy blog and you're done. No laptop required.
Scheduled maintenance
Set up playbooks for routine tasks. /run cleanup runs disk cleanup on all servers.
Real Scenario: Saturday Night Incident
You're at a party. Phone buzzes: Uptime Robot says your main SaaS is down. Old way: excuse yourself, find WiFi, open laptop, VPN, SSH, grep through 847 lines of logs, diagnose for 20 minutes. mttrly way: Pull out phone → "why is it down?" → Bro checks server, sees nginx crashed, config error line 47 → you fix typo in GitHub, /deploy → 47 seconds total. Back to the party.
“I run 4 micro-SaaS products. Before mttrly, I needed my laptop everywhere. Now I confidently leave for vacation knowing I can handle anything from my phone.”— Marcus, Serial Indie Hacker
Example: Managing 3 projects from dinner
✅ blog (Hetzner): CPU 5%, RAM 30%
⚠️ api-service (AWS): Disk 92%