Architecture

February 8, 2026

Go Desktop Agent Part 2: Redis Pub/Sub - The Nervous System

In Part 2 of our Go Desktop Agent series, we take a deep dive into Redis pub/sub — the messaging backbone that connects your infrastructure to user desktops. We’ll explore how it works, why we chose it, and where this component could evolve as the project matures.

Why Redis Pub/Sub?

When designing the communication layer for the desktop agent, we evaluated several options: WebSockets, gRPC streaming, MQTT, RabbitMQ, and Redis pub/sub. Each has merits, but Redis emerged as the winner for our MVP for several compelling reasons:

January 15, 2026

Go Desktop Agent Part 1: Architecture and Problem Space

In this first part of our Go Desktop Agent series, we’ll explore the architectural decisions and the real-world problems this agent solves.

The Problem: Reaching Users Where They Are

System administrators, DevOps engineers, and IT professionals often face a critical challenge: how do you reliably notify users about important system events when they’re focused on their work? Email gets buried, Slack messages get missed, and web dashboards require active monitoring. What’s needed is a system that can break through the noise and deliver timely, actionable notifications directly to the desktop.