Safeguard Your Platform with Alertalytix
Real-time risk intelligence and browser fingerprinting to detect fraudulent sessions and protect your users.
Why Alertalytix?
Real-Time Risk Scoring
Analyse session patterns and assign risk scores instantly to stop unauthorised access before it happens.
Privacy-Friendly & Secure
Collect only the signals needed for risk analysis. Identifiers are hashed with tenant-specific salt to meet privacy requirements.
Developer-Friendly API
Integrate risk intelligence via REST APIs and webhooks. Ship production-ready fraud defences in days, not quarters.
How It Works
Collect Signals
Capture device signals, IP reputation, velocity and behavioural data from the browser or server-side ingest endpoint.
Score Risk
Enrich events with graph insights and extract hundreds of features. Our scoring models deliver consistent risk assessments in milliseconds.
Decide Automatically
Power automated allow, challenge or deny flows with tunable rules. Trigger MFA, queue for review or block instantly.
Plug into Your Stack
Web SDK
Install alertalytix.js in minutes. The iframe bridge avoids third-party cookie issues and buffers events offline.
- Consent-aware collection with alx-consent metadata
- Automatic retry when the network drops
- Device, session and identity linking out of the box
Server APIs
Send critical events from your backend and fetch real-time decisions. Authenticate using scoped API keys and audit via webhook logs.
curl -X POST https://api.alertalytix.cloud/api/v1/events \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY' \
-d '{
"event_type": "signup",
"occurred_at": "2024-10-01T12:00:00Z",
"context": { "ip_address": "192.0.2.10" },
"subject": { "identity_key": "hashed-user-id" }
}'
Frequently Asked Questions
How is Alertalytix different from basic fingerprinting?
We combine high-entropy browser fingerprints with behavioural signals, IP reputation, velocity analysis and graph links across identities.
Can I ingest server-side events?
Yes. Use the REST endpoint with scoped API keys to send authentication, payments or support events for a unified risk view.
How do you handle consent?
Consent is enforced with metadata flags or your CMP callback. If consent is required but not granted, we skip collection entirely.
Is Alertalytix GDPR compliant?
Absolutely. Identifiers are hashed, and we plan to operate storage in the Japan region while purging partitions based on retention policies.
Quick Integration: event_id + Decision API
The client-side collector posts events to POST /collect/v1 and receives an event_id. Pass the ID to your backend and fetch the decision via GET /api/v1/events/:event_id/decision.
Sequence diagram
Alternative: server-to-server ingest
Post events directly from your backend when client instrumentation is not available, then request the decision using the same event_id.
curl -X POST "https://api.alertalytix.cloud/api/v1/events" \
-H 'Content-Type: application/json' \
-H 'X-API-Key: <YOUR_API_KEY>' \
-d '{
"event_type": "login",
"occurred_at": "'$(date -u +%Y-%m-%dT%H:%M:%SZ)'",
"context": { "ip_address": "192.0.2.10" },
"subject": { "identity_key": "hashed-user-id" }
}'
curl -X GET "https://api.alertalytix.cloud/api/v1/events/<EVENT_ID>/decision" \
-H 'X-API-Key: <YOUR_API_KEY>'
Ready to get started?
Sign up now and start protecting your platform with Alertalytix in minutes.