Device Intelligence
Site-scoped device handle with risk context
Evaluation access
PRODUCTS
Every Noxtica product, with its availability stated plainly
Pick the product that answers your question. Each page explains what it does, how teams connect it, where it stops, and whether it is offered through evaluation, controlled provisioning, or is still in development.
HOW THEY CONNECT
From evidence to the places you use it
Browser scripts, signed requests and hosted pages feed the products. You read the results in your own server, in the console, or through your own AI agents.
Where evidence comes from
Browser script
Your pages load the Noxtica collector. Optional collection follows your consent settings.
Connects to: Device Intelligence, Risk Scoring, Session Replay, Real User Monitoring
Signed agent requests
Requests that reach your domains with a signed agent identity.
Connects to: Know Your Agent
Hosted verification page
Your customer opens a single-use link that your server created.
Connects to: Identity Verification
Backend telemetry
Services that already emit OpenTelemetry data.
In development
Connects to: APM
Endpoint client
A client on a device that its owner can see.
In development
Connects to: Pulse
Noxtica products
Fraud & identity
Site-scoped device handle with risk context
Score, confidence, and named reasons
Verify signed agent requests, then observe
Hosted verification flow with a status read
Experience & observability
Replay recorded sessions beside risk and diagnostic context
Sampled web vitals, client errors and console diagnostics
AI & endpoint
Read-only console assistant for operators
Read-only MCP over the tenant's own risk telemetry
Where you use them
Your server
Authenticated lookups and event notifications. Your policy decides.
Connects to: Device Intelligence, Risk Scoring, Know Your Agent, Identity Verification
Noxtica console
Operators review risk, sessions and diagnostics within their role.
Connects to: Every product in this map
Your AI agents
Read-only MCP over your tenant's own risk telemetry, with a scoped token.
Connects to: MCP Server
Fraud & identity
Evidence about devices, risk, agents and identity checks that your own policy turns into decisions.
Risk Scoring
Score, confidence, and named reasons
Evaluation access
Know Your Agent
Verify signed agent requests, then observe
Controlled availability
Identity Verification
Hosted verification flow with a status read
Controlled availability
Experience & observability
Browser-side evidence about sessions and page performance, collected under settings your team controls.
Session Replay
Replay recorded sessions beside risk and diagnostic context
Controlled availability
Real User Monitoring
Sampled web vitals, client errors and console diagnostics
Controlled availability
APM
Planned: backend telemetry linked to browser sessions
In development
AI & endpoint
Governed ways to ask questions of your own telemetry, plus an endpoint client that is still being built.
AI Assistant
Read-only console assistant for operators
Controlled availability
MCP Server
Read-only MCP over the tenant's own risk telemetry
Controlled availability
Pulse
Planned: endpoint signals that device owners can see
In development
How we label availability
- Evaluation access
- Reached through an evaluation workspace. Contact the team to request access and confirm scope.
- Controlled availability
- Provisioned per workspace after review. Contact the team to confirm eligibility and scope.
- In development
- Being built and not generally available. Nothing on this page is a commitment on scope or timing.
BY PROBLEM
Start from the problem instead
These pages walk through a synthetic workflow for one abuse problem and name the products involved.
Talk through your use case
Tell us what you need to decide, and where. We will map it to the products that fit and say plainly what is not ready.