Roadmap

Product roadmap

The V2 "universal cockpit" ships in independent functional lots — each one shippable alone, with no imposed date milestone. The direction is clear, and so is the order. For the release-by-release detail, see the public changelog.

In progress

The lot being built right now.

  • Lot 2 — Unix Server target type + push-only agent

    The first non-mobile target type. A lightweight agent (Python, no dependencies) installs in a single command on a Debian or Ubuntu server, then pushes its system metrics, systemd service state, filtered logs and pending security updates to the cockpit. No open port on the supervised server, strictly read-only. Includes server-target creation on web and mobile, and a seed of demo servers.

Planned

The direction of the V2 "universal cockpit", delivered in independent functional lots. No firm date, but a clear order.

  • Lot 3 — Super-dashboard + app ↔ server links

    Link an app to the server(s) hosting it, and get an aggregated view: consolidated health, errors and alerts for a group of linked targets, on a single screen.

  • Lot 4 — Pro plan, quotas and payment

    Introduction of a Pro tier designed as a contribution to infrastructure costs, with transparent usage gauges, graceful degradation on overage (never a surprise charge), and access codes. The free tier stays free for standard use.

  • Lot 5 — Multi-target mobile app

    Rework of the mobile app to show apps and servers side by side, with a shared internal layer. Set up of an automated build and distribution pipeline.

  • Lot 6 — Jira, GitLab and GitHub connectors

    The three connectors currently in preview become functional: issues, sprints, merge requests, pipelines — brought next to crashes and reviews. Available on apps as well as servers.

  • Lot 7 — Zero-downtime deployment

    Industrialised releases: instrumented rolling restart to cut the unavailability window to under one second during releases.

  • Lot 8 — Complete public documentation + launch

    Install guides per distribution and per connector, quickstart per user profile, and finalisation of the legal documents (including the Pro tier terms). Coordination of the official V2 launch.

  • Lot 9 — Automatic agent updates (optional)

    A signed distribution channel so installed agents update cleanly, at the pace chosen by the administrator.

  • Beyond — databases, websites, containers

    The polymorphic base laid in Lot 1 is built to host new target types without a rewrite. Databases, e-commerce sites and Docker containers are the logical continuation of the universal cockpit.

Released

Already in production.

  • Lot 1 — The "universal cockpit" base

    v2.0.0-rc.1

    Internal rework of the data model: StatHall no longer supervises just "apps" but generic "supervised targets", ready to host servers (Lot 2) then databases, websites and containers. Transparent migration — every V1 app, connector and history is kept identical. Historical Buy Me A Coffee contributors are recognised as "Founding supporters". Health-score reliability fixes in rc.2 → rc.5 are tracked in the public changelog.

  • Before V2 — StatHall V1

    v1.0.0

    The whole inherited base: mobile app supervision (Sentry, Apple App Store Connect, Google Play, Firebase), AI review summaries, anomaly detection, crash ↔ review correlation, roadmap, multi-tenant SaaS mode and self-hosted mode, iOS/Android mobile app, marketing site. The release-by-release detail remains available in the public changelog.