Product

Evidence-first crypto migration intelligence.

Laviq organizes the path from observed runtime crypto to a reviewable migration decision. It does not collapse raw events, findings, and correlations into one unsupported claim.

Runtime Proof

Observed runtime crypto with process context.

Raw Evidence holds the captured crypto and network facts. The evidence record remains inspectable when a user needs to understand a finding.

Laviq Raw Evidence console view showing captured crypto events, selected evidence details, measurements, and a runtime call stack. — Real Laviq console screenshot · captured runtime crypto evidence from a scan run.

What was observed?

Crypto function execution and implementation identity.
Process, runtime, and library context.
Captured network negotiation evidence where available.

Migration Context

A distinct decision layer for findings, inventory, correlations, and performance.

The backend owns persistence and derived relationships; the UI presents those contracts rather than approximating them in the browser.

Findings

The risk queue used to review active concerns and next actions.

Inventory

Observed crypto, libraries, workloads, endpoints, and SBOM context.

Correlations

Backend-derived execution match context with explicit status.

Performance

Backend-owned history for observed crypto, network, and correlated behavior.

Evidence

Raw crypto and network event records from scan runs.

Reports

Shareable evidence packages for review and migration planning.

Migration context

Prioritize the work that is actually active.

Readiness, exposure, coverage, owner gaps, and active findings appear together as backend evidence context. These values should be reviewed with their evidence and coverage boundaries.

Laviq dashboard with active findings, readiness path, coverage, owner gaps, and attention feed. — Real Laviq console screenshot · backend-derived readiness and migration context.

Laviq Execution Match canvas connecting a finding, target, process, network evidence, protocol signature, execution match, and crypto evidence. — Real Laviq console screenshot · execution match is a backend-derived relationship with an explicit status.

Execution context

Trace a finding through the runtime path.

Execution Match relates the applicable evidence surfaces into a reviewable path. It is derived context, not a replacement for the underlying raw event records.

Performance Lab

Measure observed runtime crypto behavior.

Performance history is backend-owned measured data. The displayed samples, percentiles, and selected point support investigation; they do not establish broad capacity or production-wide performance claims.

Laviq Performance Lab showing ML-KEM key exchange measurements over time, related lanes, and selected performance statistics. — Real Laviq console screenshot · backend-owned measured performance history.

Laviq policy management workspace showing active protection policies for selected matching traffic and the proposed X25519MLKEM768 setting. — Real Laviq console screenshot · active policies apply to new matching traffic only.

Policy protection

Apply protection to selected matching connections.

The policy workspace shows the matching target, current configuration, proposed protection, and hit count. Its scope is explicit: the policy is enabled for new traffic that matches it.