Clear answers.
A better starting point.

Laviq helps enterprises discover active cryptography, plan workload-specific post-quantum migration, apply supported changes, and validate the result. It connects runtime evidence to dependencies and evaluates options using measurements, simulation, and controlled experiments where applicable.

An inventory describes what is packaged, declared, or configured. Runtime evidence describes activity observed while the workload runs. Both are useful: Laviq adds execution context to help your team investigate what was active during a particular collection window.

No. Laviq produces runtime evidence on supported Linux systems, including when source access is partial or unavailable. The deployment and coverage requirements still need to be checked for your workload.

Start with a representative Linux workload and a specific migration question. Review operating system, kernel, architecture, permissions, and workload requirements during scoping. Support for your particular environment should be confirmed before deployment.

The agent collects evidence about cryptographic activity without requiring private-key material. Review the collection boundaries and deployment requirements with your team before an assessment.

No. A scan describes what was captured during its collection window. An unobserved path may not have executed or may fall outside the supported coverage. Check scan status and coverage before interpreting an empty result.

No. Remediation can mean a customer-executed native upgrade, proxy protection for a supported connection segment, or supported OpenSSL implementation redirection. Each has compatibility and deployment requirements. A proxy policy does not upgrade all cryptography inside an application.

Active policies apply to new matching connections only. Review the selected target, current and proposed protection, policy status, and hits. A policy being active does not by itself establish end-to-end post-quantum protection.

Performance Lab presents measured samples and related operations collected from the workload. Use those observations to compare behavior and identify what to test next; they are not a guarantee for every environment.

Bring a representative Linux workload, the migration decision you need to make, and the people who will review the outcome. Together we scope the evidence and options to evaluate, agree on the report, and define the next action and validation needed.

An assessment focuses on a scoped migration question. A design partnership adds close collaboration and product feedback from the people working through that question, helping refine the workflow and evidence requirements.

In the authenticated Laviq Console, select an active organization API key, then open Targets → Install Agent. Use the generated command for your organization and review the installation guide before running it.

Start with security requirements and compatibility constraints. Use dependency and blast-radius analysis to identify affected relationships, then compare measured or simulated costs among acceptable alternatives. Record the test conditions and coverage behind the decision.

Supported OpenSSL implementation redirection preserves expected output and application behavior without source changes. Implementation substitution is different from algorithm substitution; it is not a demonstrated native post-quantum algorithm upgrade. Confirm supported operations and versions with the team.

Current option evaluation is operator-assisted. Automated workload-specific recommendations are a planned intelligence layer. Transparent substitution of a different algorithm, including native post-quantum algorithms, remains future research.

Before-and-after evidence can show crypto behavior or negotiation and measured costs for the evaluated environment and path. Keep original application observations, proxy results, and simulated estimates distinct. Policy status alone does not establish full-path protection.