Sumo Logic announced Sumo Logic Flex Licensing, a log analytics pricing plan that offers free, unlimited log data ingest so developer, security and operations teams can capture and analyze critical data across their enterprise.
The new pricing model removes a common cost barrier for analytics, allowing customers to take full advantage of their ever-growing volumes of data to make data-driven decisions and accelerate innovation without gaps in visibility.
Sumo Logic’s unified, scalable and high-performance log analytics platform centralizes, stores and analyzes business-critical data in one place so organizations can reduce data overload and eliminate silos between development, security and operations. By removing the cost of data ingest into the Sumo Logic platform, companies can harness the full power of enterprise-wide data for business insights without cost limitations and leverage a single source of truth for DevSecOps initiatives.
“As data continues to grow exponentially, many log management vendors are adjusting their pricing models to adapt to this growth. The problem is that these models are still based on the same limiting parameters of data ingest or compute restriction. Sumo Logic is the first to introduce a disruptive approach by associating cost with the actual value of the platform - the analytics,” said Joe Kim, President and CEO for Sumo Logic. “We believe that log analytics can be a powerful single source of truth across Dev, Sec and Ops, and organizations shouldn’t have to pick and choose which business-critical data to ingest. Our new Flex Licensing model removes the cost barriers, allowing organizations to finally centralize, store and analyze all application, infrastructure and security data in one place to drive collaboration and provide the visibility required to make rapid decisions and accelerate innovation.”
Sumo Logic’s new Flex Licensing plan aligns cost to business value to overcome today’s ever-growing data challenge by only charging customers for data storage and analytics executed. This revolutionary new consumption model provides customers with a scalable and efficient log analytics architecture that grows to manage enterprise-wide and cloud-scale log ingestion without the risk of runaway costs.
Additionally, by delivering the new financial model for log management that encourages customers to ingest all of their log data, Sumo Logic is enabling businesses to centralize all of their observability and security analytics data in one place to simplify and accelerate meantime to resolution for availability, performance, and security incidents.
As part of Flex Licensing, organizations get full access to Sumo Logic’s SaaS Log Analytics Platform with complete visibility into their applications and systems.
Key benefits of Flex Licensing and the platform include:
- No charge for log ingest: Removes cost limitations associated with pricing models that charge based on data ingest and require Dev, Sec and Ops teams to pick and choose tools and which data to share. Instead, value is directly tied to analytics.
- Straightforward pricing and platform: Simple, transparent pricing model that only charges for data storage and analytics. There are no hidden monthly charges, feature restrictions, performance tradeoffs or user limitations.
- Deeper insights through ML/AI - Flex Licensing enables powerful ML/AI capabilities out-of-the-box to solve some of the hardest operational and security challenges, including surfacing high-fidelity insights and establishing a single source of truth for developers, operations, and security teams on a scalable and high-performance platform that aligns investment and cost with business insights.
- Unified log analytics for DevSecOps: Dev, Sec and Ops teams can ingest all structured, semi-structured and unstructured data and run analytics at unmatched performance with Sumo Logic’s AI-driven log analytics platform. With one place for monitoring and securing applications, teams can break down silos, consolidate tools and expand DevSecOps transformations.
Flex Licensing is available immediately to new Sumo Logic customers and will be made available to existing customers later this year.
The Latest
IT organizations have historically measured success by how quickly they can respond when something goes wrong. The entire discipline of Incident Management has been optimized around mean time to resolution, first-response SLAs and ticket closure rates. But new research suggests that even though this is a well-executed playbook, it's no longer enough to retain customers ...
Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...
Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...
Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...