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 the conversation
2. Find laptop + network
3. VPN (if needed)
4. SSH into server
5. Reconstruct context
6. Diagnose and fix
7. Verify manuallymttrly way:
1. Open the alert
2. Review current status
3. Ask for the likely cause
4. Confirm the scoped fix
5. See verification + audit resultThe 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
Use /servers to see connected servers, then /switch to choose one and /healthcheck to inspect its current health.
Named servers
Use friendly server names such as "blog", "api", and "main-app" when choosing context. Service commands still take the service name, for example /restart nginx.
Quick deploys
After a deploy profile is configured, choose the target server and request that configured deploy in natural language from your phone.
Scheduled maintenance
Prepared maintenance actions target the selected server. For example, /cleanup creates an approval-required disk-cleanup action; it does not fan out across every server.
Illustrative Scenario: Saturday Night Incident
You're at a party. An uptime alert says your main SaaS is down. The old move is to leave the conversation, find a laptop and network, open VPN and SSH, and rebuild the incident context from commands and logs. With mttrly, you open the alert on your phone, ask what failed, review the evidence, fix the typo in GitHub, request the deploy, and see the verification without starting a blind terminal session.
Illustrative example: Managing 3 projects from dinner
✅ blog (Hetzner): online
✅ api-service (AWS): online