Bronto /  
Nitro

How Bronto became a key part of Nitro’s security toolkit

Founded
Melbourne, Australia, 2005
Switched
2025
Company Size
300 - 500

Nitro operates a global document productivity platform serving over 3 million licensed users across 157 countries, including 67% of the Fortune 500. As they transition their PDF and workflow solutions from on-device applications to a comprehensive SaaS model, their distributed infrastructure generates massive log volumes across Azure cloud services, requiring robust logging for security monitoring and compliance with HIPAA, DORA, ISO 27001, and SOC2 requirements at enterprise scale.

Bronto Comparison — Security Logs

Before Bronto After Bronto
Security logs scattered across multiple platforms (Datadog, Azure Log Analytics, S3 buckets,) Centralized logging layer with streamlined Azure Event Hubs integration
Only 3–30 days retention in Datadog due to cost constraints 365+ day retention meeting & exceeding compliance requirements
Limited retention meant data was only available for AI initiatives in a very short window Longer retention period makes log data available for a wider set of AI use cases
High-volume logs excluded from monitoring due to Datadog pricing Comprehensive ingestion of MS Defender, Entra ID, and Cisco Meraki logs
Manual log restoration from cold storage when needed Instant searchability enabling threat hunting and forensic analysis
Limited security visibility due to fragmented log storage Full incident forensics, timeline reconstruction, and behavioral baseline analysis

How Bronto helped:

Nitro implemented Bronto as their unified security logging layer, moving away from costly Datadog retention and fragmented Azure storage. Their Azure integration streams MS Defender and Entra ID logs through Azure Event Hubs directly to Bronto, while a custom Azure Container Instance with Fluent Bit collects Cisco Meraki syslog events via dedicated EventHub and Azure Function App processing. Nitro is expanding adoption across their engineering organization while maintaining Datadog for specific APM tracing and incident management capabilities.

  • Implementation: Rapid initial deployment with phased rollout across all enterprise log sources.
  • Team Adoption: Currently deployed for security and compliance workflows, with plans for broader engineering team adoption
  • Cost: Significant reduction in logging costs compared to extending Datadog retention
  • Retention: Expanded significantly, from as low as 3 days in some circumstances to 365+ days meeting HIPAA, DORA, ISO 27001, and SOC2 compliance requirements. Also opens up new use cases such as threat hunting across historical data, full incident forensics and timeline reconstruction
  • Long-term behavioral baseline analysis
  • Coverage: Comprehensive ingestion of MS Defender, Entra ID, and Cisco Meraki logs with centralized Azure Event Hubs integration
  • Performance: Improved search performance and interface responsiveness compared to Datadog for security analysis workflows

"Bronto’s long term always hot days means we can access data with sub second search, whether it’s from last week or last year. This is huge for our security and AI strategy as we continue to revolutionize how we work at Nitro taking advantage of the latest innovations in AI for everything from root cause analysis to anomaly detection.  For AI-powered analysis of our logs, data availability is key - it’s just not possible with only a few days of retention. Bronto has therefore become a key part of our toolkit when we think of log data and how it will play an important role for engineering, security and product teams going forward."

- John Fitzpatrick, CTO, Nitro