Historical PDFs — for current RC2 installation and verification use the web guides.
Official documents are available by language.
Product Overview
Product scope and core architecture.
Public Technical Whitepaper
Security boundary and technical architecture.
Release Evidence
Public release verification results.
14-Day Free Trial Guide
Installation, Trial start, and operation.
Installation & License Activation / Operations Guide
Installation, activation, and operating procedures.
Getting started
System requirements
| Windows | Windows Server 2022 AMD64 |
|---|---|
| Linux | Ubuntu 22.04 · Ubuntu 24.04 · Debian 12 · Rocky Linux 9 · AlmaLinux 9 · AMD64 |
| Python | CPython 3.12 |
| Cryptographic runtime | OpenSSL 3.5.8 |
| FastAPI | Import ODRE PQC, register the Core boundary with install(app), then connect Gateway and the Commercial gate in main.py. Configure Gateway identity, keys, trust, protected routes and startup/shutdown; Core registration alone is not the complete integration. |
| Permissions | Sufficient rights to install the package, initialize trusted local runtime state, and satisfy platform-specific trust checks. |
| Other environments | Not verified in the public v0.2.9 scope. |
Installation, activation and runtime checks
Verify the customer archive and the independently approved verifier kit first. Install into a new protected immutable directory, then follow the RC2 Native installation guide.
- Compare the complete ZIP SHA, then verify CMS, the pinned root and signer, signed CRL, publication manifest, inventory, envelope and policy-pin consistency.
- Preserve existing identity, License, Unit, Lease and device state. Do not reinitialize an existing installation or copy private material to another device.
- Trial and Paid use the same ODRE PQC 0.3.1 / RC2 ZIP. Downloading starts neither a Trial nor a payment.
- verify checks Core after existing Lease admission. Verify the actual Gateway → Core → Protected Handler path separately.
Existing Wheel installation guide
Install and verify the official bundle, connect the server integration, activate, then test the running path. Existing Android, iOS and Web clients need no code changes or SDK replacement. Follow the release-specific guide for exact installer and Gateway API names.
- Verify and install the official bundle; check dependencies.
- New installation only: odre-pqc init.
- Run odre-pqc doctor.
- Run odre-pqc verify (independent Core self-test).
- In main.py, register Core with install(app), then connect Gateway and the Commercial gate; configure identity, trust and protected routes.
- Complete Trial activation or, for a paid license, odre-pqc-commercial activate and web approval.
- Check odre-pqc-commercial status; for paid activation confirm ACTIVE, LEASE_VALID, integrity PASS and Unit allocation.
- Start the customer server and Gateway private Core.
- Run odre-pqc status against the intended running Core.
- Smoke-test Gateway → Core → Protected Handler, including fail-closed behavior; do not confuse this with Core self-tests.
- Open Production traffic only after all applicable gates pass.
Installation & connection
Installation
The commands in this section apply to existing Wheel installations. For Native Bundle, follow the dedicated installation guide. RC2 installation and Native commands
Verify the customer archive and the independently approved verifier kit first. Install into a new protected immutable directory, then follow the RC2 Native installation guide.
- AMD64: Windows Server 2022 / Ubuntu 22.04 / Ubuntu 24.04 / Debian 12 / Rocky Linux 9 / AlmaLinux 9; CPython 3.12; OpenSSL 3.5.8.
- Verify the customer archive and the independently approved verifier kit first. Install into a new protected immutable directory, then follow the RC2 Native installation guide.
- Compare the complete ZIP SHA, then verify CMS, the pinned root and signer, signed CRL, publication manifest, inventory, envelope and policy-pin consistency.
- init creates a Native device identity. Use it only for a new installation. doctor checks the signed runtime without activation. verify checks Core after existing Lease admission. Verify the actual Gateway → Core → Protected Handler path separately.
- status reads the Native state. Trial and Paid activation use the installed Native launcher and its approved local trust configuration.
Production integration
The commands in this section apply to existing Wheel installations. For Native Bundle, follow the dedicated installation guide. RC2 installation and Native commands
The confirmed Core registration entry point is intentionally small:
from fastapi import FastAPI
from odre_pqc import install
app = FastAPI()
install(app)
verify checks Core after existing Lease admission. Verify the actual Gateway → Core → Protected Handler path separately.
License delivery
For a normal Paddle purchase, the email entered at checkout is re-verified through the signed payment process and used for license delivery. The browser return page alone is not treated as payment proof.
Operations & updates
Status
The commands in this section apply to existing Wheel installations. For Native Bundle, follow the dedicated installation guide. RC2 installation and Native commands
status reads the Native state. Trial and Paid activation use the installed Native launcher and its approved local trust configuration.
Verify
The commands in this section apply to existing Wheel installations. For Native Bundle, follow the dedicated installation guide. RC2 installation and Native commands
verify checks Core after existing Lease admission. Verify the actual Gateway → Core → Protected Handler path separately.
Operations
A normal shutdown stops new protected admission, drains bounded in-flight work, disposes sessions and leases, closes native resources, releases locks, and records stopped state. Crash recovery re-checks ownership, stale locks, sessions, and partially initialized runtime before returning to Ready.
Signed local updates
The configured customer updater checks approved local input every 15 seconds. It validates signatures, integrity and compatibility before passing accepted input to the local AUM. This release does not download new releases from a central update server.
Problem solving
Doctor
doctor checks the signed runtime without activation.
Troubleshooting
- Hash mismatch: stop installation and obtain the artifact again through the official delivery route.
- Unsupported OS, architecture, or Python version: do not describe the environment as verified; contact technical support before deployment.
- Doctor or verify failure: keep protected traffic disabled until the reported condition is resolved.
- Missing license email: do not purchase again; use the recovery page or license support.
- Operational instructions not covered publicly: use the customer guide supplied with the release.