Skip to main content
OCTOVO
Download

Download

One build, and it is stated here in full

There is exactly one package: macOS, Apple Silicon (arm64). It is signed with an Apple Development certificate and it is not notarised — so on first launch macOS reports an unknown developer. Right-click once, choose “Open”, confirm — and never again.

unterschrieben fehlt

One seal is there: the signature. The second — notarisation — is missing.

System
macOS, Apple Silicon (arm64), from macOS 11.0
Version
0.1.38 (Channel Test)
Built on
11 August 2026
File
OCTOVO-0.1.38-arm64-mac.zip
Size
212.6 MiB
Signature
Apple Development certificate
Notarisation
no — there is no Developer ID certificate

Download for macOS (212.6 MiB)

Checksum

With this you check that the file wasn’t changed on the way. It is created at build time and belongs to exactly this build — if it doesn’t match, it isn’t this package.

sha512-wjIqQ57aGAj69ImGVUG2MEKllTHsCYV0CmqIXH1EqoXelc+RiNAZmtHyQ+cSx9TSOA7vwtxdaWb8ILlwOPX+1w==

How to work it out on your own machine — in the same notation (sha512, base64):

shasum -a 512 -b OCTOVO-0.1.38-arm64-mac.zip | cut -d' ' -f1 | xxd -r -p | base64

Windows and Linux

They don’t exist — not yet, not at all

Windows Linux gibt es nicht

There is no package for Windows or Linux.

  • Windows

    It isn’t being built. The build instructions of the app do contain the entries for a Windows package, but it has never been built or signed.

  • Linux

    It isn’t being built. Neither AppImage nor .deb nor .rpm exists — not even as a test build.

We deliberately name no date. Windows lacks a code signature, without which every downloaded program gets stuck in SmartScreen; macOS lacks notarisation. Both are certificates that first have to be obtained — and a promised month that then slips by is worse than this answer. What gets finished appears in the changelog.