← Tessen

Status

Checked at build time: 2026-09-22

What a buyer can actually verify about this download, right now — sourced from the same manifest the app itself reads, and from the checks this site's own deploy process runs before anything goes live.

This page is static. It is not polling anything live and it does not refresh itself. It states what was true and what was checked the last time the site was built and deployed — the same posture as a changelog, not a dashboard. If you want the current numbers straight from the source, the links below go directly to the files a buyer's Mac (or Tessen itself) actually reads.

The download being served

Version 2.0.6

Served from gettessen.com/releases/manifest.json, which names the exact build number, release date, and a SHA-256 checksum of the .dmg — open it any time and compare it against the file you downloaded.

Notarized by Apple, ticket stapled

Every release is signed with a Developer ID certificate, submitted to Apple's notarization service, and shipped with the resulting ticket stapled to the app — so Gatekeeper can verify it offline, on first launch, with no network call of its own. See the Install Guide for what that means for you on first open.

Licence activation

The activation endpoint ships in every deploy

Licence activation and renewal are Cloudflare Pages Functions deployed alongside every version of this site — not a separate service that can be up while the site is down, or down while the site is up. Their behaviour is exercised by this site's own test suite (activation, renewal, verification, and the trial handoff each have a dedicated test file) before any deploy is allowed to proceed.

This page deliberately does not claim the endpoint answered a live ping just now — that would be a "live" claim on a static page, and the two rules this site is written under forbid exactly that shape of overclaim. If you want to know it is reachable at this moment, the app tells you the same way any buyer would find out: try "Activate" in the Hub.

What the deploy gate checks before anything ships

Every deploy to this site runs the same six steps, in order, and stops on the first failure. None of them are optional and none of them run only sometimes:

  1. Rebuild the whole site from source, so what ships is never hand-edited output.
  2. Scan the entire tree for secrets before anything is packaged.
  3. Refuse to ship any page that still carries an unfilled double-brace placeholder — an undecided value stays visibly undecided, it never ships as a silent guess.
  4. Run the full test suite (both the website's and, separately, a battery of browser tests against the built pages) and stop on the first failure.
  5. Refuse to upload any .dmg that is not notarized and stapled, for every .dmg in the release — not just the newest one.
  6. After upload, fetch the live page back and check it is byte-for-byte the copy that was just built, so a deploy is never reported successful while an edge server is still serving something older.

This is the same list, in the same order, every time — it is code, not a checklist someone might skip when in a hurry.

Tessen needs no server to dictate

Recognition, formatting, and typing your words at the cursor all happen on this Mac. None of it depends on gettessen.com, or any server, being reachable. The network calls this product makes are about the purchase, not the dictation, plus one more you control yourself: trial start, licence activation, an occasional licence refresh near expiry, an update check, and — only if you choose to download an additional speech-recognition engine — a speech model download. Five calls, and that list is exhaustive. None of them carries your voice or your words.

Full detail, including which file on this Mac each of those five calls touches: the Privacy Policy.