Updates
Niah checks for updates on its own and applies them on restart. Everything here also works manually if you would rather control when it happens.
Release track
Builds ship on the stable update channel, and the product is currently in its Beta release. There is no separate insider or nightly channel — everyone on a given platform receives the same build.
How updating works
The app periodically asks the update service whether a newer build exists for your exact platform and current version. If none does, the service answers that you are up to date and nothing happens. If one does, the update downloads in the background and applies the next time you restart.
| Update service | https://api.niah.si/code/updates |
|---|---|
| Channel | stable |
| Artifacts | https://api.niah.si/code/releases/<version>/artifacts/ |
Both hosts must be reachable for updates to work. On a restricted network,
allow outbound HTTPS to api.niah.si.
Updating manually
Download the current build from niah.si/download and install it over the top of your existing copy. Your settings, extensions, and sign-in are kept — they live outside the application itself.
.dmg. An app launched from a disk image cannot replace
itself, so automatic updates silently fail to apply.
Managed and offline environments
For fleets, deploy the .pkg on macOS or the .msi on
Windows through your existing management tooling, and pin an explicit version
rather than relying on in-app updates.
Artifact URLs are immutable once published, so they are safe to reference from a provisioning script or image build:
https://api.niah.si/code/releases/<version>/artifacts/Niah-<version>-<platform>.<ext>
To discover the newest published version programmatically, read
https://api.niah.si/code/releases/latest.json. The full list of
platform suffixes is in
Installation.
Checking your version
Open the About dialog — Niah › About Niah on macOS, or Help › About on Windows and Linux — to see the version and release track you are running. Include that when reporting a problem.