Pageviews tell you someone arrived; Pug is an open-source product analytics platform that shows what people actually did next, across events, funnels, retention, and user flows. Capture events from browser, Android, Flutter, Node, Go, or Ruby SDKs into an ingestion pipeline that enriches each hit with geography, user agent, bot detection, and web attribution automatically. Identify and alias the users behind events, then open a profile to see traits, sessions, and the full activity history of a person. Build insights as trends, funnels, retention cohorts, segmentation, Sankey user flows, and top-K breakdowns, with filters and period-over-period comparison on every chart. A web analytics overview is generated from your events with visitors, sessions, pageviews, bounce rate, and traffic sources, requiring no tile wiring. The live view plots every current visitor on a real-time world map, down to the person and the event they just fired. Compose dashboards from insight and markdown tiles on a time-windowed grid that analysts rearrange without touching ingestion. Erase a person's events and profile on request to satisfy GDPR and DPDP data-subject obligations. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Real-time alerts from your own infrastructure to your phone, with no Firebase, Pushover, or third-party push service in the path: Gotify is a simple, self-hosted notification server written in Go. The model is deliberately minimal: senders push messages with a single HTTP POST to the REST API, receivers subscribe over a WebSocket stream, and a clean React web UI manages the pieces. Senders are namespaced as "applications," each with its own token, so your backup script, Uptime Kuma, CI pipeline, and cron jobs each get an identity, an icon, and independently revocable credentials - centralized alerting from many services with per-source management. Messages carry a title, body, and priority level that maps to notification importance on the client. The official Android app (on both F-Droid and Google Play, notable for working entirely without Google Play Services) shows push notifications for new messages; the web UI itself supports Web Push in the browser; and gotify/cli pushes messages from shell scripts with one command. A server-side plugin system adds custom behavior, and the whole thing runs as a single small binary with SQLite by default - near-zero resource footprint. Because dozens of tools (and Apprise) speak Gotify natively, it slots in as the notification hub for an entire homelab or ops stack.

One notify() call is all your product needs to reach users on push, email, SMS, chat, and webhooks, with NotifKit deciding how and when each message travels. List the channels in the order you prefer and NotifKit tries each in turn, so a failed push quietly becomes an SMS or an email instead of a lost message. Per-user preferences, consent, and quiet hours in each user's own timezone hold non-urgent sends until morning, while critical messages such as one-time passwords travel their own lane immediately. Templates, multi-step workflows that wait days or block on events, scheduling, throttling, and deduplication all run behind that single call, defined in TypeScript and kept in your repository. Delivery logs record every attempt, and the admin dashboard shows a live activity feed, queue depth per priority lane, workflow runs step by step, and a replayable dead-letter queue. Several products can share one deployment as separate projects with their own API keys, rate limits, and data, and any service can call the REST API without the TypeScript SDK. Ask an AI assistant why a password reset never arrived by connecting the built-in MCP server to Claude Code, Cursor, or another MCP client. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Powering notification delivery for thousands of organizations with over 39,000 GitHub stars, Novu is the open-source communication infrastructure that eliminates the need to build separate integrations for every messaging channel. The TypeScript-based platform provides a single API endpoint that routes notifications across In-App Inbox, Email via SendGrid, Mailgun, AWS SES, and Postmark, SMS through Twilio, Vonage, and Plivo, Push via Firebase Cloud Messaging, Expo, and APNS, and Chat through Slack, Discord, Microsoft Teams, and WhatsApp. The embeddable React Inbox component delivers real-time WebSocket-powered notifications with read/unread states, action buttons, and user-controlled preferences directly inside your application. The workflow engine orchestrates complex multi-channel delivery with conditional branching, time delays, digest batching to reduce notification fatigue, throttle controls, and per-step channel fallbacks. Novu Connect introduces Agent Communication Infrastructure enabling AI agents built with LangChain, Claude, or custom frameworks to hold threaded two-way conversations with humans across any supported channel through a single conversation model with identity resolution and credential management. The backend runs on Node.js with NestJS, MongoDB for notification storage, Redis with BullMQ for job queuing, and Socket.io for real-time delivery. Self-hosting deploys via Docker Compose with the dashboard accessible at port 4200. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

ntfy sends push notifications to your phone or desktop with a single curl command: publish a message to any topic and every subscriber receives it instantly, no signup or API key required. Over 31,000 GitHub stars and 106 releases since 2021 back a server supporting five priority levels mapped to distinct notification sounds and vibration patterns, emoji tags for visual classification, click actions that open URLs when tapped, and up to three action buttons per notification for view, HTTP callback, broadcast, or clipboard copy operations. File attachments push images from surveillance cameras, documents, or any binary payload directly to mobile devices. Subscriptions work through JSON streams, Server-Sent Events, WebSockets, or raw text, with server-side filtering by priority, tags, and message ID. Authentication enforces topic-level access control through Basic Auth, Bearer tokens, or query parameters, with a built-in user and ACL management system. UnifiedPush compatibility lets ntfy serve as a push distributor for Mastodon, Matrix, and other federated services. Web Push via VAPID keys delivers browser notifications without the mobile app. The server ships as a single statically linked Go binary or Docker image supporting amd64, armv7, and arm64 architectures, consuming 30-50 MB RAM at idle with SQLite-backed message caching. Integrations include Grafana, Prometheus Alertmanager, Uptime Kuma, Home Assistant, and Ansible Semaphore. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 / GPLv2 dual-licensed.

One REST call, 130+ notification services: Apprise API wraps the well-known Apprise library in a lightweight Django/Gunicorn microservice, so "send an alert" works the same whether it goes to Slack, Discord, Telegram, Teams, email, SMS, Pushover, or PagerDuty - each addressed by a simple URL scheme. It solves the credential-sprawl problem cleanly: instead of embedding provider tokens in every app, cron job, and CI pipeline, you centralize them here and everything else just POSTs a body and title. Two modes cover every workflow. Stateless calls to /notify carry target URLs in the payload (or fall back to a default set via APPRISE_STATELESS_URLS); stateful mode stores named configurations server-side under keys, so /notify/{KEY} fans out to everything registered - with tag-based routing (comma for OR, space for AND) selecting which endpoints fire per message. Messages take info, success, warning, or failure types in text, Markdown, or HTML, with attachments up to a configurable size. A built-in web UI manages and tests configurations, APPRISE_CONFIG_LOCK makes the store read-only, service allow/deny lists restrict which schemes work, webhook remapping adapts third-party payloads, and a Prometheus /metrics endpoint watches the gateway itself.

With 7,400+ GitHub stars and a feature set that replaces seven separate SaaS subscriptions — Pingdom for monitoring, StatusPage.io for status pages, PagerDuty for on-call, Incident.io for incident management, Datadog for APM, Loggly for logs, and Sentry for error tracking — OneUptime delivers every tool your reliability team needs in a single open-source platform that is genuinely 100% open source under Apache 2.0 (not open-core). Uptime monitoring runs synthetic checks against websites, APIs, ports, SSL certificates, and DNS records from distributed global probes with configurable intervals and thresholds. Branded status pages publish automatically when monitors detect issues, notifying subscribers via email, SMS, webhook, or RSS without manual intervention during an outage. On-call scheduling routes alerts through escalation policies to the right engineer via phone call, SMS, push notification, Slack, or Microsoft Teams. The incident management workflow handles declaration, triage, communication, resolution, and post-mortem generation in a unified timeline. APM collects traces and metrics via native OpenTelemetry integration — no proprietary agents required — while log management provides full-text search and alerting. An AI agent continuously monitors telemetry data, identifies root causes, and opens GitHub pull requests with proposed fixes for review. Deploy via Docker Compose or Kubernetes Helm charts with a Terraform provider for infrastructure-as-code configuration. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

With over 31,000 GitHub stars and native OpenTelemetry support that eliminates vendor lock-in from day one, SigNoz delivers full-stack observability covering metrics, traces, and logs in a single pane of glass without the per-host pricing model of commercial APM platforms. The platform ingests telemetry data through the OpenTelemetry Collector, supporting auto-instrumentation for Java, Python, Node.js, Go, Ruby, PHP, and .NET applications with zero code changes required for basic tracing. ClickHouse serves as the columnar storage backend, providing fast aggregation queries over billions of spans and log lines with configurable retention policies and tiered storage. The distributed tracing view renders flame graphs and Gantt charts showing request flow across microservices with latency breakdowns, error rates, and p99 percentile calculations. Custom dashboards support PromQL and ClickHouse SQL queries with time-series charts, bar graphs, tables, and value widgets. The log management pipeline supports structured and unstructured logs with full-text search, log pipelines for parsing and enrichment, and correlation with traces via trace IDs. Alert rules can be configured on any metric or log query with notification channels including Slack, PagerDuty, OpsGenie, webhooks, and email. The exceptions monitoring module automatically groups and tracks application errors with stack traces, occurrence counts, and first-seen timestamps. Service maps visualize inter-service dependencies with real-time latency and error rate overlays. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed with an enterprise edition available.

With 20,500+ GitHub stars and over 6,000 organizations running it in production — including a Fortune 100 company ingesting more than 4 PB per day — OpenObserve is the open-source observability platform that replaces your entire Datadog, Splunk, or ELK stack with a single Rust binary deploying in under two minutes. Apache Parquet columnar storage with zstd compression on S3-compatible object storage delivers 140x lower storage costs than Elasticsearch while providing better query performance on a quarter of the hardware. Ingest logs, metrics, and distributed traces via native OpenTelemetry OTLP endpoints with no vendor lock-in. Query logs and traces with standard SQL, metrics with SQL or PromQL — no proprietary query language to learn. The built-in dashboard builder offers 19 chart types including time-series graphs, heatmaps, gauges, tables, and top-K lists with drag-and-drop layout combining data from all signal types. Data pipelines process, enrich, redact, or normalize ingestion streams using Vector Remap Language for real-time transformations including PII redaction and logs-to-metrics conversion. Real User Monitoring captures frontend performance with session replay. The Service Catalog provides topology-based trace analysis with side-panel drill-downs into database queries and error details. Alerting supports real-time and scheduled rules with SQL and PromQL conditions. Native multi-tenancy isolates organizations and streams with complete data separation. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPLv3 licensed.

HyperDX correlates logs, metrics, traces, session replays, and errors in a single interface so engineers can resolve production incidents in minutes instead of hours. Nearly 10,000 GitHub stars reflect its role as the integrated UI layer for the ClickStack blueprint endorsed by ClickHouse. The platform connects to any ClickHouse cluster as its storage backend, working with existing table structures without requiring data migration or proprietary ingestion formats. An intuitive Lucene-like search syntax supports full-text queries and property filtering like level:err or service.name:api without needing SQL, while native JSON string querying and event delta analysis surface anomalies in high-cardinality datasets. One-click cross-signal correlation lets you jump from a log line to its distributed trace, from a slow span to associated logs, or from a frontend session replay to the backend errors it triggered. The OpenTelemetry Collector accepts telemetry via OTLP on gRPC port 4317 and HTTP port 4318, supporting automatic instrumentation for Node.js, Python, Java, Go, Ruby, and browser applications. APM tracks HTTP request latency, database query duration, and external service calls with trace waterfall visualizations. Configurable alerts trigger via webhook, Slack, PagerDuty, or email when thresholds are breached. Deploys via Docker Compose with ClickHouse, MongoDB, Redis, and the OpenTelemetry Collector. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

The de facto dashboard of observability: Grafana is the open-source frontend that turns the data stores you already run into interactive graphs. It does not store metrics itself; it connects to the data stores you already run and turns their contents into interactive dashboards. Supported sources number over 150 via plugins: Prometheus, Loki, Tempo, InfluxDB, Elasticsearch, MySQL, PostgreSQL, Microsoft SQL Server, AWS CloudWatch, Azure Monitor, Google Cloud Monitoring, and many more. Dashboards are built from a large library of panel types (time series, heatmaps, tables, gauges, logs) with template variables for reusable, parameterized views. Unified alerting evaluates rules against any connected data source, not just Prometheus, and routes notifications to Slack, PagerDuty, email, and other channels with grouping and silencing - unlike Prometheus Alertmanager, a single rule can combine a Loki log pattern, a PostgreSQL query result, and a CloudWatch metric. Dashboards serialize to JSON and data sources configure via provisioning files, so the entire observability setup can live in Git and deploy repeatably across environments. Explore mode adds ad-hoc querying outside dashboards, with split view for correlating a metric spike against the matching log lines, and access control spans organizations, teams, folder permissions, and OAuth, LDAP, and SAML integration. Written in Go and TypeScript, AGPL-licensed. Self-hosting gives you unlimited users, dashboards, and queries at flat hosting cost, without Grafana Cloud's usage-based pricing.

Backed by 44,000 GitHub stars and trusted by over four million developers, Sentry is the debugging platform that captures errors, traces, replays, profiles, and metrics from your applications and connects them all through distributed tracing. The error tracking engine captures full stack traces with source context, breadcrumbs, and automatic demangling for native crashes, while intelligent grouping consolidates duplicate events into actionable issues with regression detection and automatic assignment. Performance monitoring instruments your frameworks automatically, capturing every database query, API call, cache hit, and queue operation as spans within distributed traces that flow across frontend, backend, and mobile boundaries. Session Replay produces video-like recordings of real user sessions showing DOM interactions, network requests, console messages, and errors on a synchronized timeline, with AI-powered summaries that describe what happened without watching the full replay. Continuous profiling captures CPU execution data at the function and line level for Node.js, Python, iOS, and Android, linking slow spans directly to the exact code responsible. Cron monitoring tracks scheduled jobs for failures, missed runs, and duration anomalies. The alerting engine fires notifications through Slack, PagerDuty, Opsgenie, and webhooks on new issues, regressions, error spikes, or when latency and crash-free session rate thresholds are crossed. Self-hosted deployment runs as a Docker Compose stack with PostgreSQL, ClickHouse, Kafka, Redis, and Relay. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. FSL licensed.

Exceptionless has earned over 2,400 GitHub stars and has been processing production errors since 2014 as the real-time event monitoring platform that captures far more than crashes. Built with ASP.NET Core on Elasticsearch for storage and Redis for caching, Exceptionless ingests exceptions, log messages, feature usage events, broken links, and custom event types through official SDKs for JavaScript, Node.js, .NET Core, ASP.NET, WPF, Web API, WebForms, Console apps, and React Native. Automatic event stacking groups related occurrences by exception type, message, and call stack into single actionable items, while manual stacking keys let developers create custom groupings for specific features or workflows. The real-time dashboard displays Most Frequent, Most Recent, and New event views with filtering by project, date range, environment, and custom tags. Stack management tracks resolution status with version-aware regression detection that automatically reopens resolved issues when the same error surfaces in a newer release. Webhook integrations connect to Slack, Discord, and external services through Zapier for automated issue tracking in GitHub Issues and Jira. Per-project notification settings control email and chat alerts for new errors, regressions, and critical events. OpenTelemetry support captures distributed traces alongside error data. The v8.6.0 release introduced a hosted Model Context Protocol server at the /mcp endpoint, enabling AI tools to query error data via OAuth-authenticated access. Deploy via Docker with the exceptionless/exceptionless image alongside Elasticsearch and Redis. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

When a production alert fires at 3 a.m., Regen is the self-hosted on-call and incident management platform that makes sure a human answers it, keeping alerts, incidents, schedules, and escalations on one shared timeline instead of split across three tools. Alerts stream in from Prometheus Alertmanager, Grafana, AWS CloudWatch, or any webhook, and deduplication collapses repeat firings before Regen opens an incident automatically; responders can also declare one by hand and let AI draft the title and summary. Layered on-call rotations absorb overrides, holidays, and leave, while multi-step escalation policies with timeouts keep paging the next person until somebody acknowledges, so a critical page never dies in one inbox. The incident timeline syncs to Slack and Microsoft Teams, where bot commands acknowledge, escalate, and post updates without leaving chat, and Telegram notifications cover teams that live there instead. One-click summaries and handoff digests brief the incoming shift, editable postmortem drafts are assembled from the timeline using your own templates, and similar past incidents resurface with what worked last time. AI is bring-your-own-key through OpenAI, Anthropic, or a local Ollama model, and the platform loses nothing core if you never enable it. Schedules and escalation policies import in one click from PagerDuty, Grafana OnCall, or Opsgenie, SAML single sign-on through Okta, Azure AD, or Google Workspace is free, and nothing caps your incidents, schedules, or postmortems. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

OpsiMate gives on-call teams one queue for alerts that would otherwise arrive in five different dashboards, each demanding attention in its own tab. Connect Grafana, Datadog, Zabbix, Uptime Kuma, Google Cloud, or any custom webhook source and watch incoming alerts land in one table with their source, service, severity, tags, and status attached. Filter the noise down to the team or service you own, group related alerts so one incident does not look like forty separate emergencies, and use mute policies when a known problem should stop paging people. Acknowledge work with one click, assign ownership so nobody wonders who is responding, resolve alerts from the same screen, and follow deep links back into Grafana or Zabbix when you need the original chart or trigger. Let supported integrations auto-resolve alerts when the underlying monitor recovers, and use root-cause notes and insights to keep the next responder from starting at zero. Discover services running in Docker, Kubernetes, and Linux virtual machines so the alert queue stays connected to the infrastructure behind it. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Huginn has established itself as the definitive open-source automation engine for developers who refuse to hand their workflow data to third-party cloud services. The platform lets you build agents that scrape websites, monitor RSS feeds, track weather via APIs, watch Twitter streams, aggregate news, detect price changes, and trigger notifications through email, SMS via Twilio, Slack webhooks, or social media posts to Twitter and Tumblr. Each agent creates and consumes JSON events, propagating them along a directed graph where complex multi-step workflows emerge from simple single-purpose components. The web interface provides visual agent management with drag-and-drop scenario building, real-time event logs, scheduling controls, and a built-in agent library covering dozens of use cases out of the box. Huginn supports Liquid templating for dynamic event transformation, regex-based content extraction, JavaScript-based data manipulation, and HumanTaskAgent for crowd-sourced workflow steps. Custom agents can be packaged as Ruby gems and loaded via the ADDITIONAL_GEMS environment variable without modifying core code. Deployment options include Docker with the official huginn/huginn all-in-one image or huginn/huginn-single-process for production multi-container setups with PostgreSQL or MySQL backends, plus native support for Heroku and OpenShift PaaS platforms. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.