Do large reports multiply quota through panel fanout?
No. A report counts once when the canonical report shell is opened. Internal panels, charts, and subordinate endpoint calls are not separate billable units.
Practical answers for teams that want to consume Syndu reports at scale while keeping the business flow simple.
No. A report counts once when the canonical report shell is opened. Internal panels, charts, and subordinate endpoint calls are not separate billable units.
No. The product is intentionally web-first. Buyers who need mass consumption can scrape or agent-run the report pages directly and budget by daily quota.
No. Successful login, post-login operations, payment flows, dashboard activity, and websocket control traffic are kept out of the reporting pipeline.
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.
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.
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?