Logz.io & AWS Marketplace
Consumption-Based Pricing FAQs

Logz.io Consumption-Based Pricing provides the most flexible, efficient observability pricing on the market today – enabling customers to pay for precisely those Open 360 platform services they use, preventing onerous overages and tailoring spend to their unique requirements. By paying for only the data you actually ingest into the platform and actively use to conduct your critical observability processes, you no longer run the risk of overestimating what you might need or paying for costly overages when conditions change.

Unlike traditional models that require organizations to estimate the level of observability data they will utilize ahead of time and negotiate a flat rate based on projections, Logz.io’s consumption-based pricing eliminates the guesswork and transitions observability into a real-time cost model. In addition to mapping spend to actual consumption to accurately control costs, this approach enables customers to adopt a more dynamic approach to using every element of the Open 360 platform.

Nearly every organization has unique seasonal or operational spikes in observability data [ex. holiday shopping season, production changes]. Instead of attempting to project the impact of these real-world events, pay for exactly the data needed to account for the demands of your environment and business on an ongoing basis. Eliminate the potential for costly overages and ensure that you have precisely the level of required observability.

By launching this model, organizations gain immediate flexibility that supports their observability journey by moving data wherever they need to in the platform to support their evolving requirements, without incurring additional costs or negotiating additional licensing agreements. This is particularly useful for organizations seeking to rapidly expand their use of full observability, such as through adoption of the App 360 and K8s 360 solutions which deliver unified, cross stack insights and troubleshooting.

Using the AWS Marketplace  for Logz.io, one  unit is equal to $0.01 USD. This means that Logz.io reports your monitory consumption to AWS and your cost is calculated in this manner.

For this volume of data, a team will need to pay for 1GB ingested into the platform (the cost of adding it to the Open 360 platform ingestion pipeline without storing the data for analysis) which will cost AWS 10 units or $0.10 USD.

In this scenario (storing the data in the platform for ongoing analysis at the fastest querying speeds, with full dashboarding etc.) you would need to pay for 82 AWS units or $0.82 USD.

In this scenario (keeping the data on hand in the fastest querying tier, with full dashboarding etc.) you would pay for 1GB index (7 more days) which will cost 21 AWS units or $0.21 USD.

In this common scenario (including ingestion, indexing and retention in the hot storage tier for of two weeks [most common use case]) the total cost would be 103 AWS units per 1GB (which is $1.03) 

Your account can be cancelled at any time via the AWS Marketplace manage subscriptions in your AWS account.

Your account plan can be upgraded or downgraded at any time via the AWS Marketplace manage subscriptions; however, the overarching value of Logz.io Consumption-Based Pricing is that you don’t need to upgrade your plan if you want to send more data, simply send more data and your bill will be updated based on what you sent to the platform.

Yes, you can pre-negotiate any level of data directly with Logz.io or prepay in the AWS Marketplace. Schedule a call with sales to pre-negotiate your data needs. 

Yes, volume discounting can be negotiated directly with Logz.io. Schedule a call to discuss your needs. 

Yes, customers can update or re-renew at any time based on their changing requirements or the instance that it is clear that they are going to go over their previously planned data levels.

Yes, customers can roll over up to 20% of their overall data if it goes unused, annually.