Overview & core concepts

What the platform is, the tier model, and how storage degrades gracefully.

Passwordless OTP sign-in, the limits that apply, and disposable-email handling.

Plans, prices & quotas

Every SKU and quota, read live from the platform catalog.

Every tool on the platform, grouped by category, listed live from the catalog.

Multi-tenant log ingestion, detection and AI triage — with API examples.

QR enrolment, the installable PWA, posture signals and fleet reporting.

Website monitoring & agent

Register a site you own, prove control of the domain, install the PHP agent, and watch events arrive.

Seats, invitations, and the Team Security Center.

Free modules, progress sync, AI tutor, and verified certificates.

Authentication, every endpoint, rate limits and status codes.

Security & privacy model

What is never stored, the defences in force, and how to report a vulnerability.

Quick reference (printable)

Every tool on one page: tier, what it takes, whether it uses AI, and whether it stores anything.

What each panel means: usage, quotas, pack balances and account state.

The problems users actually hit, and what to do about each.

How prepaid passes work, what expiry means, receipts, and where the binding terms live.

// tool reference · Vulnerability & Assessment

AI Vulnerability Triage Pro

Paste nmap/nikto/ffuf output for de-duplicated, prioritized triage with false-positive filtering and remediation.

Open AI Vulnerability Triage →

What it does

Takes raw scanner output and answers the question the scanner cannot: which of these actually matter here. It dedupes, correlates, and re-prioritises by your exploitability and business context rather than by CVSS alone.

When to use it

A scan returned hundreds of findings and you have an afternoon.
You need to justify a fix order to someone who will ask why.

Inputs

Field names are the actual form parameters, verified against source.

Field	Type	Required	Notes
scan_raw	textarea	required	Scanner output — Nessus, OpenVAS, Trivy, npm audit, etc.
fmt	select	optional	Source format hint.

What you get back

A deduplicated, ranked list with the reason each item moved up or down.

Worked example

Input

CVE-2026-1111  CVSS 9.8  openssl      (host: web-01)
CVE-2026-2222  CVSS 7.5  log4j-core   (host: web-01)
CVE-2026-1111  CVSS 9.8  openssl      (host: web-02)
CVE-2026-3333  CVSS 5.3  curl         (host: db-01)

Output (abridged)

TRIAGED -- 4 findings -> 3 unique, reordered

1. CVE-2026-2222  log4j-core  CVSS 7.5   <- FIRST, despite lower CVSS
   ON CISA KEV. Actively exploited. Reachable from your web tier.
   Exploited-at-7.5 beats not-exploited-at-9.8.

2. CVE-2026-1111  openssl     CVSS 9.8   (web-01, web-02 -- deduped)
   High severity, no known exploitation. Patch this cycle.

3. CVE-2026-3333  curl        CVSS 5.3
   db-01 has no egress. Not reachable. Patch when convenient.

The scanner sorted by CVSS. That is the wrong order.

How it works

Deterministic parsing and dedup, then AI prioritisation informed by KEV membership and reachability.

Limits

Read live from the platform configuration.

Rate limit

5 requests / 10 minutes

Limitations — what it does not do

Prioritisation depends on the context you provide. It does not know your network topology unless you describe it, so reachability judgements are advisory. Verify before deferring anything.

Privacy

Scan output is sent to the AI provider.

Standards

CVSSCISA KEVEPSS concepts

← All tools Manual home