Please reach us at contact@stryqbyte.com if you cannot find an answer to your question.
No. Files move directly between sender and receiver. Optional rendezvous and relay services exchange metadata only (e.g., registration, NAT traversal) — not file payloads.
No product is CMMC certified — organizations are. Stryq provides controls that support many NIST SP 800-171 requirements when deployed as documented.
No. LAN-only deployments work with pairing codes. Internet-facing features (rendezvous, relay) are optional and customer-hosted.
Windows 10 22H2+, Windows 11, and Windows Server 2022+. macOS and Linux are not in v2.3.
Offline seat token plus machine-bound activation. Licensing is validated on the device — file payloads and live license checks are not sent to Stryqbyte during transfers.
Activations bind to MachineGuid. Clones need new activations — by design.
Yes. Install a production .pfx for receivers via Security Setup.
Inbound UDP on the receiver listen port (default installer: 8500). Optional TCP on listen port + 1 when TLS fallback is enabled. Rendezvous 5055, relay 5056 if those services are deployed.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.