- Type
- not stated
- Format
- Two shapes. The classification asset is a structured reference dataset: URL or domain to category mapping across 100+ categories, with human-readable category descriptions and dated version releases, delivered as product data. The activity asset is transactional log data — per-device, per-user visit and search-query records with timestamps — held in each customer's own database, exportable as reports for audit and incident response but not aggregated centrally.
- Volume
- The classification asset is large and countable: millions of URLs across 100+ categories, versioned continuously — plausibly tens to hundreds of millions of mapping rows with revision history. The activity asset is genuinely unknown: if it accumulates at all, 700+ organisations of mixed school and workplace size would generate hundreds of millions to billions of visit and query records annually, but under this deployment model those rows live in customer databases and the vendor's aggregate hold is likely near zero. Do not price an activity corpus here without explicit confirmation.
- Users
- 700+ organisations (vendor-stated on the page) across both education and workforce deployments — but these are institutional licences, not individual registrations, and the education subset is smaller than the total because the company's core market is employee monitoring. Basis: the figure is printed on the page; the entity record shows 58 staff in Toronto, consistent with several hundred mid-sized deployments rather than a mass-market base.
- History
- 20 years
- Update frequency
- not stated
- Growth
- Active and recently refreshed — site assets carry mid-2026 dating, category documentation shows versioned releases indicating ongoing taxonomy maintenance, and the sales motion is a self-serve 14-day trial with no credit card, which is a growth-oriented product-led posture. Corporate status is recorded as merger or acquisition rather than a funding round, so ownership has changed; 58 staff in Toronto suggests a mid-sized company integrating into a larger group rather than an independent scaler.
- Launched
- Est. mid-to-late 2000s for BrowseControl and BrowseReporter, based on the classic Windows-agent-plus-on-premises-console architecture, Active Directory and Citrix/Terminal Server dependency, and the entity record's long registration history — all hallmarks of pre-cloud endpoint management. The self-serve trial and current web assets indicate modernisation of go-to-market rather than a recent product start, so the underlying codebase and category database are likely 15-20 years old.
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated