Documentation

Activation and Entitlement

What pyvorin-native 1.0.9 does when you activate: the Ed25519-signed lease, device binding, gate semantics, anti-rollback, and the offline grace table per tier.

7 min read

Implementing Pyvorin at the Edge

Edge deployment with Pyvorin Native 1.0.9: compile on an x86_64 build host, ship the compiled cache, and activate per device within its offline grace window.

LicenseValidator API Reference

Every LicenseValidator class, enum and environment variable, including local file format and the local-vs-remote validation cascade.

12 min read

Network Requirements for Pyvorin

Every endpoint pyvorin-native 1.0.9 contacts, when each fires, offline grace windows, air-gap implications, TLS, and the env overrides that redirect traffic.

7 min read

Pyvorin in Air-Gapped Environments

Compilation needs no network at all. Licensing degrades slowly: offline-valid leases keep passing, and grace runs from 24 hours to 90 days by tier.

Pyvorin in Docker: Best Practices

Compile in the builder stage, ship the disk cache in the image, and activate at container start. The Docker practices that matter for Pyvorin Native 1.0.9.

Running Pyvorin Natively on Your Own Hardware

pyvorin-native has no remote compile mode to opt into — local compilation is the architecture. What runs on your hardware, and what the only network calls do.

Security and Source Privacy

What pyvorin-native 1.0.9 sends off your machine, what never leaves it, the pyvorin-thin warning, and the set_privacy opt-out — verified on the installed build.

Security Best Practices

The verified security posture of pyvorin-native 1.0.9: what the product guarantees, what it does not, and the practices that keep it sound.