◎
The application notices
ORINEX checks whether a newer version exists and shows it inside the product. The check carries no Workspace data — only whether there is something newer than what you are running.
Updates
You decide when the software changes.
ORINEX Workspace tells you a new version exists. It does not install it. Your team picks the week, which for a school district is usually the difference between a routine upgrade and a bad Tuesday.
How updates reach you
Three steps, and you control two of them.
◇
You decide
Nothing downloads or installs on its own. An administrator chooses to fetch the release and chooses when to apply it. Skipping one is a legitimate answer.
▦
You can verify it
Installers are code-signed and timestamped, so Windows will show you the publisher before anything runs. Ask and we will give you the SHA-256 of the exact build you were sent.
What you are told
Change arrives with an explanation.
Maintenance releases go out as fixes and improvements are ready, rather than on a calendar that makes you wait for something you need. Every release reaches you with notes describing what changed and why — sent to the people running it, not left for you to find.
- Release notes go to the districts running the software, with the SHA-256 of the exact build.
- The documentation installed with a build always matches that build, so the help center is never describing a version you don't have.
- Anything that changes behavior your team relies on gets called out before the upgrade, not discovered after it.
See it on your own domain.
Thirty days, your own Workspace, no card. Tell us about your district and we will set it up.