Edge suppression
Server nginx suppresses websocket routes, business routes, and authenticated requests from the access logs that are later fetched to the laptop for processing.
Account, quota, payment, documentation, and websocket traffic is kept out of the reporting universe. The reporting pipeline is reserved for observed network behavior, not customer account operations.
Server nginx suppresses websocket routes, business routes, and authenticated requests from the access logs that are later fetched to the laptop for processing.
Laptop-side ingestion repeats the same rule: private surfaces and websocket handshakes are omitted before `logmap_db` and again before `logfacts`.
Failed logins stay separate as security telemetry. They do not belong in the public report universe and are not mixed into the report rollups.
Syndu exposes a dimensional risk surface across network entities and geography: ip address, subnet, ISP, ASN, organization, city, region, and country.
Syndu reports are external context pages for monitoring, hygiene review, and decision support. They complement SoC and SIEM processes rather than replace them.
The product is designed for organizations that already have web-scale collection and AI processing capacity. Syndu sells quota on report access rather than an API entitlement model.
Syndu uses the web's underlying metadata to simplify customer onboarding and quota ownership. Good network metadata improves both attribution quality and product fit.
Syndu identifies the consuming organization from network metadata when possible, then counts only canonical report lookups against the daily quota.
Syndu prices report consumption as daily report-shell volume. The quota covers the canonical report page, not the smart-panel fanout behind it.
Registration unlocks the quota dashboard, plan selection, and the subscription flow while keeping report delivery quota-based.
This is a custom alert message.
Are you sure you want to proceed?