Skip to main content

The route to a stable release

This roadmap describes intended work, without promising release dates. Current behavior is documented in Features and Release notes.

Available in the source preview​

Local SSH sign-in, reviewed application discovery, service operations, service and host measurements, journal viewing, website checks, audit history, application removal and server deregistration are implemented. A Windows desktop setup script creates a shortcut and tray launcher.

Next: an easier Windows download​

Prepare a package that includes the required runtime. Test first launch, local HTTPS trust, reopening, quitting, updating and removal from a clean Windows account. Keep private state separate from installed application files.

Before a stable support claim​

Add and test SSH key authentication. Verify permissions, lost connections, host-key changes, service failures and timeouts against disposable Ubuntu services. Exercise Nginx and SQL Server operations in an isolated lab.

Review the command and credential boundaries independently. Publish the exact tested operating systems, package checksums, signing information and known limitations.

After the first stable release​

Prioritize clear user feedback: setup difficulties, confusing status information, missing diagnostics and maintainability. Wider platform support needs its own tests and documented startup behavior.

Suggest a focused improvement through GitHub Issues. Keep infrastructure credentials and private host details out of proposals.