ORINEX Workspace was created from real K-12 IT experience and designed around the work school technology teams handle every day. It is purpose-built for K-12, with workflows shaped by the realities of managing Google Workspace in a district environment.
Google gives administrators real power over a Workspace domain, and the serious way to reach it is a command line. That is fine for one careful person on a quiet afternoon. It is not fine for offboarding two hundred students in June, and it is not something you hand to a new hire in their first week.
ORINEX runs on a Windows machine your district controls, using your district's Google credentials. We could have built a hosted platform. Holding a thousand districts' student directories in one place is a target, and it makes every privacy review harder than it needs to be.
Updates never install themselves. A release lands when an administrator chooses to apply it, which means nothing shifts under your team during the first week of school.
ORINEX can delete mail and deprovision accounts in bulk. Our documentation and our security page say so plainly, because you are going to find out either way, and it is better that you find out from us.
When you contact ORINEX, you are talking to people who understand the product and the environment it runs in. You will not be pushed through a generic tier-one script before someone looks at the actual issue.
If something is wrong, it gets investigated by the people closest to the product and the problem.
A 30-day evaluation, on your infrastructure, installed by your team.
