Private beta · invite required
StackEye combines hosted website and API checks with Linux host health from Station. Team and Enterprise beta customers can also use a support-assisted relay for active HTTP, TCP, Ping, and DNS checks from inside their networks.
Already have an invite? Create your account.
The category difference
External uptime monitoring answers an important question: can a hosted checker reach this public endpoint? StackEye keeps that view and adds Linux host signals; support-assisted Team and Enterprise beta relays can add active checks from inside a private network.
Hosted external monitoring
Ideal for confirming that a website or API is reachable from outside your network. UptimeRobot and StackEye both do this.
A public check cannot directly reach a private address that has no public route.
StackEye
Install Station for Linux CPU, memory, filesystem, network, and sensor health. Support-assisted Team and Enterprise beta relays run supported checks from private locations.
These are separate installed roles today. The published Station artifact is not marketed as the private-check runner.
What StackEye monitors today
The differentiated product is a connected monitoring workflow—not a longer list of generic alerting features.
Run hosted checks from three US regions—East, Central, and West—and require a majority of at least two reporting regions to confirm a DOWN state.
Use Station for Linux host monitoring. Team and Enterprise beta customers can use a separate, support-assisted private relay for active internal checks.
Attach monitors to the services and devices they represent. Model parent-child dependencies so a failed upstream probe can suppress downstream alert noise.
Keep detection and incident communication together, without pretending StackEye is a logs, traces, or full APM platform.
Derived from the real UI
A monitor uses managed public regions or the support-assisted private path. Private work never falls back to managed public probes, but strict site affinity is not promised during beta: when a configured region has no active bound relay, current assignment logic can use another active private relay in the same organization.
The example is sanitized, but its labels, source model, check types, and states mirror the current product.
Installed monitoring roles
The product model is converging, but the published artifacts are not yet one unified runner. The site now reflects that boundary.
Enroll Station and manage host identity, status, version, lifecycle, CPU, memory, filesystem, network, and supported sensor signals.
Configured Team and Enterprise beta relays execute HTTP, TCP, Ping, and DNS checks and submit results over an outbound connection.
The current self-serve private-relay installer path is being repaired, and the published Station release does not include its private-IP execution fix.
Already use UptimeRobot?
UptimeRobot is a capable hosted public monitor with multi-location checks, API assertions, alerts, incidents, teams, and status pages. StackEye adds Linux host health through Station and, for Team and Enterprise beta customers, active checks through a support-assisted private relay.
Beta plan configuration · live checkout not verified
These values come from the current application source. They are not presented as a verified purchasable catalog until the live Stripe checkout is tested. Every CTA joins the invite-gated beta.
Configured paid amounts still require live Stripe-catalog verification. The billing UI labels Starter with a 2-minute minimum, but the monitor form does not expose that option, so no Starter cadence is promised here. Annual values, status-page allocations, Enterprise terms, and beta-specific overrides remain unpublished.
Scope you can trust
Technical buyers should not have to reverse-engineer the boundary between a shipped capability and a roadmap idea.
Questions technical buyers ask
Both products can monitor public websites and APIs from hosted locations. StackEye also ships Station for Linux host health and offers active HTTP, TCP, Ping, and DNS checks through a support-assisted Team and Enterprise beta relay. UptimeRobot’s heartbeat monitor can accept outbound liveness check-ins from internal jobs; that is different from a relay initiating a test against another target.
No. The relay connects outward to the StackEye control plane, receives assigned work, and submits results. The private targets do not need a public route.
Not as a generally available production claim today. Station can be deployed as a Kubernetes DaemonSet for Linux node-host monitoring. A separate cluster controller and topology UI exist in development, but the current production self-serve cluster flow is not complete.
Support-assisted Team and Enterprise beta relays support HTTP/HTTPS, TCP port, ICMP Ping, and DNS resolution. SMTP is available for public monitoring but is intentionally excluded from private-region execution. Fresh self-serve relay onboarding is not currently presented as working.
StackEye is in private beta. Join the waitlist for access; if you already have an invite code, use the account-creation link in the hero.
Private beta
Join the beta to evaluate hosted checks and Linux host health—or discuss the support-assisted Team and Enterprise private-relay path while self-serve onboarding is repaired.
Join the beta waitlist