My scrapers run on PythonAnywhere. My phone runs Termux. I wanted them to talk to each other. The standard options all had the same problem: they required infrastructure I didn't want to maintain. Firebase — cloud lock-in, SDK overhead, costs money at scale Ngrok — exposes a port on my phone, dies when the tunnel resets A VPS with Redis — another server to maintain, SSH into, keep alive Webhook to
ZopNight v2.0: The Control Layer Your Cloud Bill Has Been Missing We've been watching cloud bills grow for years. Dashboards got prettier. Alerts got louder. The bills kept climbing. ZopNight v2.0 is our answer to why: the problem was never visibility. It was control. This release ships the full four-layer stack we believe every multi-cloud team needs: discovery with 14-day metrics, policy that
I needed to coordinate background scripts running across different machines. The obvious answer was Redis. Everyone uses Redis for this. The tutorials all use Redis. The Stack Overflow answers all say "just use Redis." So I looked at what deploying Redis would actually cost me: A running Redis server I had to maintain A broker to connect workers to it Celery or RQ on top of that Memory-based stora