Switching
The reason people cannot leave Windows is rarely the operating system. It is one application they need, and one login their employer controls. We are building for both.
Windows applications
Windows programs run through a compatibility layer that translates the calls they make into the Linux equivalents. There is no Windows virtual machine underneath and no Microsoft code involved.
| No second licence | Nothing of Windows is being run, so there is nothing extra to buy. |
|---|---|
| Fast | The application's instructions run directly on your processor. Only the calls into the operating system are translated, which is why this is quicker than a virtual machine. |
| Sandboxed | Each application gets the file and network access you grant it. A Windows program on Orynr has no more of your machine than anything else does. |
| Consent applies | The same gate governs it. A Windows application asking for something privileged raises the same card as anything else. |
Being straight about this matters more than the marketing does.
For those cases a Windows virtual machine remains the honest answer, and Orynr can host one.
Active Directory
Orynr will join an Active Directory domain using the standard, long-established Linux path rather than anything bespoke.
| Authentication | Kerberos, the same protocol Windows itself uses. |
|---|---|
| Identity | SSSD, so domain users and groups exist on the machine as they do elsewhere. |
| File shares | SMB, so the drives people expect mount where they expect them. |
| For administrators | Machines appear in the directory and can be managed through the tooling already in place. |
Today Orynr runs the Linux application ecosystem, a full Chromium browser with Chrome and Edge extensions, and local AI. That covers a great deal of what most people actually do.