Documentation

Install the thin client, activate your licence, and run your first compiled script in under two minutes.

The Pyvorin CLI communicates with the compile and licence APIs. Configure endpoints via environment variables or a local config file.

• Default: https://api.pyvorin.com
• Env override: PYVORIN_API_URL
• Config file: ~/.pyvorin/config.json if present

When enabled, Pyvorin refuses to fall back to CPython. If a script contains unsupported constructs, compilation halts with a clear error instead of silently degrading to interpreted execution.

Use in CI pipelines and performance-critical deployments where fallback is unacceptable.

Pyvorin reports every fallback event honestly. When the native compiler cannot handle a construct, the thin client records the reason code and sends it to telemetry.

• Reason codes are stable and documented.
• Aggregated in your dashboard for auditing.
• No performance claims are made on fallback workloads.

Some dynamic Python constructs cannot be statically compiled. Pyvorin falls back to CPython for these with full transparency.

• Multiple inheritance & complex metaclasses
• Runtime exec() / eval()
• Complex descriptor protocols
• C-extension modules without native equivalents

All published benchmarks follow an honest methodology: native backend only, no fallback, warm-up runs, and statistical reporting.

• 46 canonical + 20 industry + 19 domain benchmarks
• Correctness validated against CPython output
• Speedups reported as median of 10+ runs
• Fallback workloads excluded from headline figures

Pyvorin only claims speedup on code that compiles natively. Marketing claims are gated by the safe_claims policy.

• Headline speedups = native-only median
• Fallback rate disclosed per workload
• No claims on experimental or beta passes

Understand the difference between native-compiled execution and honest fallback to CPython.