Smarter Pricing, Built for Your Needs

Log Management is priced on the amount of log data you send (measured in GBs) and how long you decide to keep it. Most of our customers retain their log data anywhere from 3-90 days. Learn how to reduce your log management costs with Data Optimization Hub, Cold Tier, LogMetrics, and Archive & Restore.

Infrastructure Monitoring is priced on the average amount of unique time-series metrics you send to Logz.io per day. The metric data retention is fixed at 18 months by default.

A unique time-series metric is a distinct and individual measurement that is continuously monitored over time. CPU and memory measurements for one VM represent two time-series metrics, while CPU and memory for five VMs represent 10 time-series metrics. Learn how to reduce your metrics volume – and therefore Logz.io costs –  with Logz.io’s Data Optimization Hub.

Distributed Tracing is priced on the amount of spans (spans are the building blocks of traces) you ingest in Logz.io every month. Use the Tracing Sampling Wizard to easily configure sampling rules in OpenTelemetry to control the volume of data ingested into Logz.io.

The span data retention is fixed at ten days by default.

Like Log Management, Cloud SIEM is priced on the amount of log data you send (measured in GBs) and how long you decide to keep it. Most of our customers retain their log data anywhere from 7-120 days. Learn how to reduce your Cloud SIEM costs with the Data Optimization Hub.

Logz.io reduces customer costs by aligning the price of data with its value. Useless data can easily be removed with Data Optimization Hub. On average, our customers remove 32% of their data and costs with this feature. For the data you keep, you can reduce storage costs with Multi-tiered Storage, LogMetrics, and Archive and Restore depending on the data’s use case.

Yes. The prices on this page represent Logz.io’s costs for the aws-us-east region. If you’d like to have your data hosted in other AWS regions or with other cloud providers, the cost will vary. See our docs to view a complete list of our supported cloud providers and regions. Contact us for pricing in other cloud regions.

Both. The monthly plan is 1.2x the cost of the annual plan.

No. Custom metrics and system metrics are priced the same.

Customers who ingest more data than their subscription plan permits will be charged On Demand pricing for the excess data. The On Demand plan is 1.4x the cost of your subscription plan.

The customer’s subscription plan will be measured against the actual data volume ingested to Logz.io every day, and the total difference will be calculated at the end of the month.

For example: if a customer commits to ingesting 5GBs of log data per day with their Logz.io account, but they ingest 10GBs one of the days, then 5GB will be charged via On Demand pricing accordingly.

Logz.io makes it easy to segregate your data across teams and provides a single view to monitor and control costs across every team. Set data caps to prevent specific teams from exceeding your organization’s data and cost commitments.

LogMetrics significantly reduce the cost of logs that provide their value through visualization (as opposed to search). LogMetrics are billed as normal time-series metrics. See the Infrastructure Monitoring pricing for LogMetrics costs.

Logz.io Log Management: You will have the ability to ship your data in excess of the above subscription plan(s), subject to an additional payment of 1.4x the cost of your subscription.

Logz.io SIEM: You will have the ability to scan your data in excess of the above subscription plan(s), subject to an additional payment of 1.4x the cost of your subscription.

Logz.io Distributed Tracing: You will have the ability to ship your data in excess of the above subscription plan(s), subject to an additional payment of 1.4x the cost of your subscription.

Logz.io Infrastructure Monitoring: You will have the ability to ship unique metrics in excess of the above subscription plan(s), subject to an additional payment, as follows:

• At the end of each calendar month, Logz.io will calculate the daily overages (based on the difference between the Actual Daily Unique Metrics Usage as defined below and the Number of Unique Metrics per Day as stated above), and multiply it by the On Demand fees, which are 1.4x the cost of your subscription costs.
• Actual Daily Unique Metrics Usage: Logz.io shall calculate the actual number of unique metrics that were shipped to the Logz.io Platform on an hourly basis, as measured by the Logz.io Platform. At the end of each day (measured from 00:00 UTC to 23:59:999 UTC), Logz.io shall average the number of unique metrics per hour and that average will be the “Actual Daily Unique Metrics Usage”.

At the end of each calendar month, Logz.io will calculate the On Demand fees that are due for that month, which will be invoiced at the end of the month.

Yes! Once per calendar month, you may provide a 7 days written notice to your account manager notifying them that you wish to re-distribute capacity allocation across Logz.io products (Log Management, Distributed Tracing, Infrastructure Monitoring, and Cloud SIEM) within your subscription plan. Capacity reallocation has no impact on the total net price of your Logz.io plan.

Capacity reallocation is only available for paying customers on an annual subscription.

Yes. We offer tailored pricing for high-volume usage. Contact our Sales team to discuss your needs and explore available discounts.

We believe the impact of consumption-based pricing is, in a word, monumental. It eliminates the upfront guesswork necessary to estimate and control observability costs. By paying for only the data you ingest into the platform and what’s needed to support your critical observability processes, you no longer run the risk of paying for overages when conditions change. From seasonality to evolving architecture, you’re covered.

Moreover, the greatest benefit of consumption-based pricing is that you only pay for what you use, giving your team full control over spending and the ability to set hard limits. We know that while most organizations do not review spending on a daily basis, some days require more data than others. By adopting the consumption model, inevitable spikes in your data will not incur costly on-demand fees – with overall utilization measured across the entire term of your contract.

As organizations seek to expand their observability practices, traditional pricing can serve as a hurdle to adopting additional data streams and unified use cases. Logz.io’s consumption-based pricing removes these obstacles, allowing organizations to adopt a single model for every form of telemetry and evolve their spending to support their current requirements.

Compared to traditional subscription pricing – where you have to assess the unique utilization of logs, metrics and traces, and face limits if you want to start sending more metrics and traces, and fewer logs – now you have the flexibility to adjust your use to suit your immediate requirements. With consumption based pricing, you commit to a single figure upfront, allowing you to decide however you want to leverage that budget across the different telemetry types.

Never. Logz.io’s 24/7 in-app free customer support applies, as always. Our support team is available worldwide at all hours and every customer, no matter how big or how small, has someone assigned to guarantee success at all times.

Logz.io provides in-depth data utilization monitoring within the platform. Detailed dashboards document every element of your data consumption and related costs. And don’t forget our Data Optimization Hub which provides hands-on capabilities to actively reduce your data consumption and spending at any time. In this way, Logz.io gives you the ability to continuously control spending and ensure you always stay within your budget.

Always. If your team utilizes all of the data they have been provided upfront, you can always add capacity to your existing contract without incurring any overage or on-demand type charges; early renewal is also an option. Just reach out to us.

We’re here to support your growing requirements. Customers can upgrade their parameters at any time based on their changing requirements. Additional data can be added quickly to your contract at any time.

Again, we’re here to make sure that your unique requirements are always being supported. If you need additional data, Logz.io can support this in a number of ways, from adding data on a pay-as-you-go basis, to negotiating a change to your initial contract. It’s also worth noting that you can closely limit your data utilization to stay within your desired range, and budget.

Logz.io offers a range of data retention and storage alternatives, from our Hot Tier to our low cost Cold Tier which reduces the budgetary impact of compliance logs or aging logs without significantly impacting query speed.

Yes. Our account team is uniquely qualified to work with you to help determine the specific level of data you need to support your existing and future requirements. We’ll work closely with you to ensure that you’ve created the best scenario to optimize your use of the platform and data, and ensure alignment with your budget.

Yes. While we rarely see customers make this change after realizing the benefits of consumption-based pricing, we are here to support your evolving vision at any time.

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.

Learn more about how consumption pricing works with AWS.

Tokens are the building blocks of AI processing (roughly 750 words per 1,000 tokens). We bill in units of 1 million tokens to provide transparent and scalable pricing for high-volume users. This includes both the prompt you send (input) and the AI’s response (output).

An invocation is counted every time an AI Agent (like the RCA Agent) is triggered—whether via an automated alert or an API call.