Back to projects
2026

DigiPulse

Uptime monitoring SaaS: event-driven architecture — Laravel (Octane, Reverb) + Filament dispatch checks through Redis to a lightweight Go worker; an MCP server exposes monitoring data to AI assistants; Telegram/email alerts
DigiPulse
SaaSLaravelGoMonitoringMCPRedisEvent-driven

Uptime monitoring SaaS — 60-second checks, SSL expiry tracking, Telegram and email notifications. The admin panel and core backend are built with Laravel (Octane, Reverb websockets) and Filament, while the monitoring engine is a separate Go service. Includes Google OAuth sign-in and Cloudflare Turnstile integration, plus an MCP server that exposes monitoring data directly to AI assistants. Self-hosted on Proxmox.

Key Features

  • Dedicated Go engine - availability checks run in a separate Go service, so constant 60-second polling never slows down the Laravel app
  • Real-time dashboard - Reverb websockets push status changes to the UI live, no manual refresh
  • Octane + Filament - resident-memory Laravel with a full admin panel for monitors, contacts and alert rules
  • MCP server - monitors and incidents are queryable from AI assistants (Claude, Cursor) via the Model Context Protocol
  • Google OAuth + Turnstile - passwordless sign-in and bot protection on public forms
  • Self-hosted - deployed on a Proxmox homelab I manage end-to-end

Tech Stack

  • Backend: Laravel (Octane, Reverb websockets)
  • Admin Panel: Filament
  • Monitoring Engine: Go (separate service)
  • Database: PostgreSQL
  • AI Integration: MCP server
  • Infrastructure: Self-hosted on Proxmox

Like what you see?

Tell me about your project — I'll propose an architecture and estimate within 24 hours.
Yurii Mokryi • © 2026