Originally posted at samiryuja.dev.
A few months ago I set up a soccer-digest bot that sends me a Telegram message every few days with fixtures, results, transfer news, and manager changes. It started as a tmux session running Claude Code on a small Linux server, fired by a cron job. It worked. It also went down occasionally, and I had no good way to inspect what it was producing.
I wanted to do two things at once: make it more reliable, and turn it into something more interesting than "one bot sending one report." The result is Futbol Report — a scheduled job on AWS that sends the same prompt and search context to four different language models (Claude, Kimi, Qwen, Gemma) every three days, stores all four reports in Redis, and renders them side-by-side on this site with live voting.
This post is about how it works, what I learned from running it, and the deployment war stories — the bits that are usually edited out of "here's my side project" writeups.
What the comparison shows
