Changelog

Every Tessera release, newest first. Tessera checks for new versions in the background and shows a banner in the dashboard when one is available. You can turn that check off in Settings.

Download the current version from the download page.

1.0.4

Released 21 September 2026

New

• A fleet overview at the top of the dashboard: overall uptime, a status breakdown you can click to filter the list, an uptime trend, and tiles for incidents, mean time to recovery, average and 95th percentile latency, certificates expiring within 30 days, and endpoints in maintenance. Choose a range of 24 hours, 7 days or 30 days.
• The check timeout is now configurable. Set a default under Settings, and override it on any individual target. Useful for endpoints that respond quickly but take several seconds to finish sending their response, which could previously be reported as failures.

Changed

• Uptime is now measured from when an endpoint was added, not from the start of the reporting period. A target added part-way through a period is no longer counted as down for the time before it existed. This applies to the dashboard and to Reports.

Fixed

• The latency sparkline on each dashboard row is drawn as soon as the page loads. Previously it could stay flat for stable endpoints and was cleared whenever the page was reloaded.

1.0.3

Released 30 August 2026

Fixed

• Monitoring could stop for every target and stay stopped until the service was restarted. The web interface stayed up throughout, so the only visible signs were check times that stopped advancing and blank bars at the right-hand end of the status page.
• The underlying cause was a check that could hang forever. If a monitored server accepted a request and then stalled part-way through sending the response, the check reading it never finished and never timed out. Checks are now bounded by the check timeout no matter how the far end behaves.
• Restarting monitoring after a target was added, edited, or deleted waited for every in-progress check to finish first, with no time limit, so a single hung check blocked it indefinitely. That wait is now capped: monitoring restarts either way, and the diagnostic log records when a check had to be abandoned.

1.0.2

Released 18 August 2026

Fixed

• HTTP checks now use the port set on a target. Previously the port field was ignored for HTTP targets, so a target such as http://192.0.2.10 with port 8081 was checked on port 80 instead. If anything answered on port 80 with an error, the target was reported as down while still showing a response time. A port written into the URL still takes priority over the port field.

1.0.1

Released 10 August 2026

Fixed

• Tessera no longer fails to start when the machine's IP address changes. If the address it was told to bind to is no longer available, it now falls back to all addresses, keeps running, and records why in the diagnostic log.
• Deleting a target gives clear feedback: the button shows progress while the delete runs, you are returned to the dashboard with a confirmation, and a failed delete leaves the page intact with an error you can retry from.

1.0.0

Released 3 August 2026

Initial release.

• Monitor websites and web services over HTTP and HTTPS, any TCP service by host and port, and host reachability with Ping.
• Optional page-content checks, custom user agents, and per-target check intervals.
• TLS certificate expiry warnings before a certificate runs out.
• Email and webhook alerts, with recipients set globally, per tag, or per target.
• Maintenance windows so planned work does not page you or count against uptime.
• Local network outage detection, so a problem with Tessera's own connection is not reported as every target going down.
• Multi-user accounts with Admin and Viewer roles, two-factor authentication by email, and self-service password reset.
• Dashboard with filtering, search, tags, and latency graphs; a public status page; uptime and incident reporting.
• Runs as a Windows service, stores everything locally, and installs with a standard Windows installer.