The authorization chain

One core capability. Every piece of software is authorized, enforced, and proven, in open and closed environments.

Enclave Logic decides whether software may run. It never installs or moves your software, and it works with the tools you already use to deliver it.

• The exact software is verified and sealed, so you know what was approved for use.
• Then the approval names the person, device, or place, and an end date if you want one.
• That approval covers that target only, never a blanket "allowed everywhere."
• For closed networks, the sealed approval is carried in by hand. Nothing calls home.

• At launch, the operating system checks the chain.
• If a link is missing or the file has changed, the software doesn't start.
• Revoke the approval, and it stays revoked, even after a reboot.
• All of it works with your service desk and deployment tool. Nothing is repackaged.

• Every authorization, refusal, and revocation is recorded as it happens.
• From that record, each person counts once per product, across every network. No double counting.
• So the answer is ready for an audit, a renewal, or a publisher's question.

• Bring a closed environment on board without telling us who or what is inside it.
• Each person is counted once on the open side, where they're already known. Inside the enclave, users and devices are counted, never named.
• Authorizations are checked for tampering and reuse when they arrive.
• Works for a whole network or a single lab.

Even air-gapped. Not only air-gapped.

Today: Windows workstations and the desktop software that runs on them, on open and closed networks.