company

Closed Beta Is Open — First 20 Slots

Back to blog

The closed beta starts now. ShxrkSystems is live, the core systems are holding up under real monitors, and we are opening registration to a first wave of testers — invite-only, distributed through our Discord server.

We are deliberately starting small: up to 20 testers for the first batch. We would rather have a focused group that actually runs monitors and reports back than a large signup wave nobody can follow. Once the first batch has settled, more slots open in waves.

What you get as a beta tester

  • Full platform access — every shipped feature, not a crippled trial tier
  • Free or discounted plans — depending on your use case we set you up with a free plan or a discount matched to your monitoring needs; talk to us on Discord
  • Direct line to the developers — your reports go straight into the fix queue, not into a ticket void
  • Influence on the roadmap — the features testers actually need get prioritized for public launch

We are also setting up a structured bug bounty for beta participants — scope and rewards will be announced on Discord.

What is live right now

Monitoring from the outside

  • Uptime Monitoring — HTTP, HTTPS, TCP, UDP, DNS, SSL, SMTP, Ping, Redis, database checks, and push-based API monitoring with intervals as low as 30 seconds
  • Global Pinger Fleet — checks run from three European regions (Falkenstein, Nuremberg, Helsinki) with automatic horizontal scaling based on load
  • Game Server Monitoring — real protocol queries for FiveM, Minecraft, Rust, CS2, ARK and Valheim plus custom games, with live player counts and slot tracking — not just "port is open" checks. Query, REST API, push and TCP connect methods supported, including a drop-in FiveM resource that reports players, tick rate and resource states

Monitoring from the inside

  • Internal Agents — lightweight Go binaries you install on your own servers to monitor CPU, RAM, disk, processes and systemd units from the inside, including private-network checks that reach RFC1918, VPN and WireGuard targets no external probe can touch
  • Metric Rules — threshold alerts on agent metrics (CPU, RAM, disk, custom metrics) with duration windows and severity levels: "disk above 90% for five minutes" becomes a real incident, not a noise email
  • Agent Automation — scheduled cron-style tasks and event-driven remediation: restart services, run scripts, update packages or reboot hosts from the dashboard, gated behind step-up 2FA
  • Security Detectors — opt-in per-agent detection of failed SSH and sudo attempts (journald) plus pending package update tracking
  • Fleet Enrollment — enrollment tokens for provisioning agents via cloud-init or autoscaling groups, plus automatic discovery of services running on enrolled hosts

Observability

  • Distributed Tracing — OTLP ingest endpoint for your applications, with per-status-page ingest keys, configurable sampling, a hierarchical span waterfall, and per-service trace management
  • Error Tracing — centralized error ingestion across every service in the platform with severity, stack traces and resolution tracking
  • Audit Log — per-status-page audit trail covering configuration changes, member actions and incident operations

Incidents and alerting

  • Status Pages — public or password-protected status pages with custom domains, incident management, maintenance windows, and team access via seats and member roles
  • Incident Management — create, update, and resolve incidents with timeline updates that sync to your status pages in real time, with dependency-aware alert suppression
  • Incident Templates — pre-written incident updates for your common failure modes, so the 3 AM postmortem-style update is a click instead of prose
  • Recurring Maintenance — maintenance windows that repeat on a schedule, automatically created ahead of each occurrence
  • Notifications — email, SMS, voice calls, Discord, Slack, and webhook integrations for incident alerts
  • On-Call Schedules — escalation policies with multi-step chains (email → Slack → SMS → phone)
  • Automation Engine — event-driven workflows that trigger on monitors, agents or incidents: conditions evaluated in real time, actions from notifications to auto-created incidents. Rules are versioned, testable against historical data (backtest), and import/exportable as JSON or YAML
  • SLA Policies — named policies with per-severity response and uptime targets, assignable to status pages, with live SLA tracking and exportable reports

Platform

  • Support Tickets — multi-channel ticketing across dashboard, email and Discord with verified customer identity
  • Billing — Polar.sh-powered subscriptions with tiered plans (Free, Pro, Elite, Business, Enterprise) and SMS/Call add-ons
  • Referral Program — earn credits by inviting other users
  • 2FA & WebAuthn — full two-factor authentication with hardware key support
  • Organizations — org-level memberships and role-based access, built on the standard org → membership → role model
  • Full Documentation — guides for every feature plus an interactive API Explorer at shxrk.systems/docs

How to get in

  1. Join the ShxrkSystems Discord — invite codes are handed out there
  2. Grab a slot — first come, first served for the initial batch of 20
  3. Sign up at app.shxrk.systems with your invite code

No Discord or missed the first batch? Subscribe to the newsletter in the footer — we email subscribers when new slots open, plus major updates and the public launch announcement.

What we expect from you

This is a real beta, not a marketing demo. We ask testers to:

  1. Run real monitoring — point it at actual infrastructure, not just test endpoints
  2. Report bugs — if something breaks, tell us on Discord; every bug found now is one fixed before public launch
  3. Give UX feedback — if a workflow feels clunky, we want to hear it
  4. Push edge cases — unusual monitor setups, high-frequency checks, large status pages, game server push payloads

What comes next

There is no fixed public launch date — we open registration when the platform earns it. Between now and then:

  • Bugs reported by testers get fixed first
  • Onboarding polish continues
  • Additional pinger regions beyond Europe are on the list
  • Tester slots expand in Discord waves
  • The rebrand may land before public launch — the name on the login page could change; your data, monitors and team carry over either way

Thanks to everyone who waited for this. We would rather open small and solid than big and shaky. See you on Discord.

Closed Beta Is Open — First 20 Slots | Uptriva