Skip to content
nexarqAI

Nexarq platform

Know what changed.
Know what to do.

Application signals, control gaps and response decisions. Connected by evidence.

Explore the productRequest a walkthrough
Traffic signals become an investigation, a reviewed decision and a retained evidence record.ObserveInvestigateDecideEvidence informs the next review
nexarqplatform
Interactive preview
app.example / API monitoring
API monitoring

Endpoints & performance

api.example.com · Last 24h

Requests

216.4K

Last 24h

Healthy endpoints

10 / 12

2 need review

Needs attention

2

1 erroring · 1 slow

Origin p95

842

ms

API map

216.4K requests · Last 24h
< 1% errors1–5%≥ 5%Not measured
GET /v1/products · api.example.comGET/v1/products38.6K/v1/products · api.example.com/productsGET /v1/search · api.example.comGET/v1/search28.6K/v1/search · api.example.com/searchPOST /v1/checkout · api.example.comPOST/v1/checkout24.8K/v1/checkout · api.example.com/checkoutGET /v1/accounts/{id} · api.example.comGET/v1/accounts/{id}18.2K/v1/accounts/{id} · api.example.com/accounts/{id}GET /v1/orders · api.example.comGET/v1/orders16.4K/v1/orders · api.example.com/ordersPOST /v1/session · api.example.comPOST/v1/session12.6K/v1/session · api.example.com/sessionPOST /v1/reports/export · api.example.comPOST/v1/reports/export3.2K/v1/reports/export · api.example.com/reports/export/v1 · api.example.com/v1api.example.comapi.example.comCustomer traffic
1–7 of 12 paths
1 / 2

Across the estate

More than an incident view.

Traffic & performance

Request trends, origin errors, latency and cache behaviour.

An operating baseline

Bots & fingerprints

Related client behaviour, bot activity and source investigations.

Context for triage

CSPM

Configuration risks, affected resources and evidence coverage.

Prioritised findings. Reviewable fixes.

Developer estate

Compute footprint, configuration posture and record coverage.

Visibility into what is deployed

How it works

A signal is the beginning.

  1. Observe

    Traffic, control activity and application context.

  2. Correlate

    Historical baselines, related behaviour and prior investigations.

  3. Review

    Evidence, counter-evidence and operator judgement.

  4. Respond

    Scoped actions, approval records and a retained outcome.

AI adds context. Evidence remains visible.

Statistical detection identifies deviations. AI helps explain and prioritise them; the operator retains the review and response decision.

Investigation and reporting

Document the finding, the decision and the next action.

Use these templates to investigate an anomaly, review a rule change or prepare a service report. Each includes the evidence to collect and the checks needed before sign-off.

nexarq / investigation recordWorking template

Security anomaly investigation record

Record the affected application, compare the signal with its baseline, and document the analyst’s conclusion.

EvidenceWhat to compareRecord in the investigation
Request volumeThe selected window against a comparable baseline; include releases or campaigns that could explain a change.Window, request count, baseline and known business context.
Client and path concentrationAffected paths, source networks and repeated client characteristics.Leading contributors and whether the activity spans multiple sources.
Control and origin outcomesBlocks, challenges, allowed requests and origin errors in the same scope.Observed response behaviour and gaps in the available data.
DispositionEvidence for abuse, evidence for normal activity and anything still unverified.Conclusion, confidence, next action, owner and review date.

Before you close the record

  • The conclusion refers to the collected evidence and known limitations.
  • Normal demand and recent changes have been considered.
  • Any proposed response has a scope, owner and approval status.

An anomaly is a reason to investigate. Leave the conclusion open when the evidence does not establish a cause.

Data boundaries

Built around your organisation.

Your peopleYour organisation’s workspace
Workspace access

Clear access boundaries.

The right people see the applications and evidence relevant to their work.

Customer data boundary

Evidence stays scoped.

Your findings, investigations and reports stay within your organisation’s workspace.

InvestigationsReportsActivity

Visibility follows access permissions and available evidence.

Start with your estate

Bring the questions
your dashboard can’t answer.

  • Which applications need attention?Review traffic, anomalies and unresolved findings in context.
  • Which rules deserve a change?Inspect rule intent, effective behaviour and a ranked fix queue.
  • What can we show leadership?Carry the scope, evidence and next decisions into a report.

Let’s build what’s next

Your next move.
Engineered by Nexarq.

What needs to change in your business?

Talk to us