“I'm a hobbyist with a home lab. What can intouch do for me?”
One question, asked of a stock install. Nothing here is staged copy — this is the answer the assistant gave, played back.
For a home lab setup, InTouch basically turns your scattered cron jobs and manual checks into one place that watches everything and only bothers you when something's actually wrong. Concretely:
Turn your existing scripts into real jobs. Every cron job on the Pi, the NAS, the old laptop — becomes a workflow with a schedule, run history, result codes, and an alert when it dies instead of silently failing for three weeks.
Keep the boxes honest. A monitor can watch disk space, a service that stopped responding, a Docker container that exited, a cert about to expire, your public IP changing, or a backup that didn't run — and message you once, with the actual number, not a wall of noise.
Proper backups. rsync or S3, nightly, with retention and proof it happened — the automation almost everyone means to build and never does.
Anything with an API is fair game. HTTP/REST, SSH, Docker, SQL, MongoDB, S3, FTP, plain shell — home automation hub, a weather API, a game server status, an RSS feed. If it answers a request, it can be scheduled and alerted on.
Local AI, zero bill. If you've got Ollama running, InTouch can use it to summarize logs, classify RSS feeds, label files — no API cost, nothing leaves your LAN. Or point it at Claude/GPT/Gemini/Mistral if you want a bigger model for something.
Write your own tool if nothing fits. An IML tool is just a declarative JSON file — no compile step. Or a real Kotlin/Java plugin if you want actual code. Either way it becomes a first-class tool I can call like any other.
Alerts land in your Inbox instantly (bell icon, push on Android, PWA on iPhone), and to email/Slack/Discord/Telegram if you want them elsewhere — all outbound-only, so no public IP or port forwarding needed behind your home router.
Cost: free, runs on your own hardware, no account, no phoning home.
Want to start with something concrete — point me at a script you're running on cron now, or a service/container you want watched, and I'll build the workflow or monitor for it.
It answered like this because it knew who was asking.
The same assistant answers a shop owner about supplier price files and a sysadmin about cron sprawl. Same engine, same tools, same audit trail — sharpened to the person asking.
The same assistant, asked by someone else.
Every one of these is a stock install answering a different person’s first question. Nothing was staged and nothing was edited.