squzy.app

What It Is

Squzy is a high-performance open-source monitoring, incident, and alerting system built around the GoLang ecosystem. It is not positioned as a simple uptime checker, but rather as a composable monitoring platform covering websites, hosts, applications, incident rules, and notification management. The official messaging emphasizes that all products are fully open source, with no hidden closed-source components, and that no user data is collected. Users can deploy it in their own cloud, on their own servers, or within their own systems.

Core Capabilities

In terms of functionality, Squzy already covers core monitoring capabilities such as HTTP/HTTPS website monitoring, TCP host monitoring, gRPC application monitoring, URL monitoring within SiteMaps, and JSON Path-based numeric monitoring. In newer versions, it also includes Agent-based collection of CPU, memory, disk, and network information, as well as application monitoring for requests, tracing, databases, and frontend components. It also provides Incident Lang for defining incident rules, along with a Notification Manager. Its open protocol is another highlight: in theory, users can implement components such as storage themselves.

Open Source, Self-Hosting, and Pricing

Squzy’s key strength lies in being open source and self-hostable. The project explicitly states that it is fully opensource and fully free without any payment, which is attractive for teams with limited budgets or strong data sovereignty requirements. Compared with commercial SaaS monitoring products, it avoids sending data to third-party services. However, this also means that deployment, upgrades, alert reliability, and ongoing operations must be handled by the team itself.

Pros and Cons

Its advantages include broad functional coverage: website and TCP probing, host Agents, application monitoring, an incident rule language, and a notification module. It is also free, open source, self-hosted, and extensible. The downside is that the collected material lacks key information about deployment complexity, permission management, notification channels, visualization dashboards, cluster high availability, community activity, and commercial support. The documentation structure appears to include Fast start, architecture, Proto, Incident Rules, and other sections, but the maturity of the documentation cannot be judged from the current text alone.

Who It’s For and Access from China

Squzy is suitable for developers, SREs, or small and medium-sized teams with Go/operations expertise who want to build their own monitoring system and care about keeping data inside their own network. If a team needs an out-of-the-box hosted service, a mature ecosystem, and SLA-backed support, alternatives such as Prometheus+Grafana, Zabbix, Uptime Kuma, Sentry, or OpenTelemetry-based solutions should also be evaluated. The text does not specify accessibility from China; the reachability of the domain and GitHub links, dependency download speeds during deployment, and community communication channels should be tested in practice.