Download websites that use Loggly

About Loggly

The row worth noticing here is the vendor. The product is called Loggly and it is sold by SolarWinds, which is the shape an acquisition leaves behind in a technology profile. A brand outlives the company that built it, keeps its own documentation and its own endpoints, and goes on being recognised by the original fingerprint long after another name went on the invoice. Anyone building a spend map by vendor rather than by product will miss installs like these unless the mapping between the two is made explicit.

Loggly is a hosted log management service dating from 2010 and licensed as Proprietary, filed in our Analytics category. Log collection normally happens on servers, where an agent ships application and system logs to the vendor over a private channel. What a web crawl can see is the other half of the pipeline, browser-side error and event capture, a script on a public page sending front-end logs to the same account. Presence therefore indicates a team that extended its logging beyond the server, which is a deliberate step rather than a default one.

A site shipping front-end logs to a hosted service is run by people who treat the website as an application they operate, not as a brochure they publish. The buyer profile follows from that: engineering teams with an on-call rotation, products with a support burden, businesses where a broken checkout costs money within the hour. Log management is also priced by ingested volume, so the install implies a budget that scales with traffic and somebody who watches it.

As of September 2026 we detect the service on 294 sites, and the figure understates the customer base by a wide margin. Server-side ingestion is invisible to a crawler by definition, so a company can be a substantial customer and never appear in our data at all. What the list offers instead is the set of domains where the vendor's code demonstrably runs in a browser, an observable and verifiable subset rather than an estimate.

Two uses justify pulling the whole list rather than checking one domain at a time. Displacement selling is the obvious one, since competing observability vendors want accounts that already pay for the category and can be approached with a migration argument rather than an education campaign. The less obvious one is portfolio analysis. When a vendor with a large catalogue owns a product, buyers and analysts want to know how the installed base is distributed and whether it is growing or draining towards other brands in the same catalogue, and a question of that shape is only answerable from a population observed repeatedly over time.