Competitors

How 10x compares to other log-reduction tools: Cribl, Grepr, and Tero. The short version: 10x cuts the bill without throwing data away by default, and reduces inside your own environment rather than a vendor cloud.

How does 10x compare to Cribl?

What Cribl is: a data pipeline you configure separately for each log source. It cuts volume by dropping log lines or replacing groups of them with rolled-up summaries.

Keeping your data: Cribl only lowers your bill by dropping lines or rolling them into summaries, and both throw the original lines away. If you keep every line intact, Cribl saves nothing, so you trade completeness against cost. 10x can lower the bill while keeping every line, and it drops or samples only when you choose to. It groups your logs into patterns (a pattern is one kind of log line, all the lines that say the same thing with different timestamps and IDs), and for each pattern it picks the cheapest way to keep that line, based on the log tool you use:
Compact (shrink the line where it sits): on Splunk, self-hosted Elasticsearch or OpenSearch, and ClickHouse, 10x shrinks each line to a fraction of its size, and your tool still stores it, searches it, and shows the full original line.
Tier down (move the line to a cheaper storage class): when your tool sells a lower-cost storage class you can still search, like Datadog Flex or CloudWatch Infrequent Access, 10x moves the line into it.
Offload (park the line in storage you own): with any tool, 10x sends the line to an S3 bucket (cheap cloud storage) in your own account. When you need those lines again, you fetch the exact originals back instantly, with no slow restore step and nothing loaded back into your log tool.
Getting data back: Cribl's only way to retrieve archived data is its Replay feature, which reprocesses the data and loads it back into your log tool, where it counts again as billable volume.
Setup and upkeep: with Cribl you build a reduction pipeline for each source, and you revise those pipelines whenever a log's format changes. 10x needs no per-source pipeline: it decides what to do with each pattern by itself, and you set a budget for your log spend and approve the plan it proposes.
Pricing: Cribl charges by the volume of data it processes, so a tool bought to lower your data bill costs more as your data grows. 10x charges a flat fee per node (a node is a machine, host, or pod running a log collector), the price is listed publicly, and it does not rise as your log volume grows.

How does 10x compare to Grepr?

What Grepr is: a service you send your logs to. It cuts the feed reaching your log tool by sampling it and replacing groups of lines with summaries.

Where your logs go: Grepr reduces your logs inside its own cloud, so the content leaves your environment to be processed. 10x reduces logs inside your own infrastructure, so the log content never leaves your environment to be cut.
Keeping your data: Grepr samples the feed to your log tool and replaces groups of lines with summaries, keeping the full lines only in its own data lake. 10x can keep every line, and drops or samples only when you choose. It groups your logs into patterns (a pattern is one kind of log line, all the lines that say the same thing with different timestamps and IDs), and for each pattern it picks the cheapest way to keep that line, based on the log tool you use:
Compact (shrink the line where it sits): on Splunk, self-hosted Elasticsearch or OpenSearch, and ClickHouse, 10x shrinks each line to a fraction of its size, and your tool still stores it, searches it, and shows the full original line.
Tier down (move the line to a cheaper storage class): when your tool sells a lower-cost storage class you can still search, like Datadog Flex or CloudWatch Infrequent Access, 10x moves the line into it.
Offload (park the line in storage you own): with any tool, 10x sends the line to an S3 bucket (cheap cloud storage) in your own account. When you need those lines again, you fetch the exact originals back instantly, with no slow restore step and nothing loaded back into your log tool.
Getting data back: when you investigate an incident, Grepr copies the relevant full lines back into your log tool, which charges you to take in that volume a second time.
Setting and proving the cut: with 10x you set a budget for your log spend and approve the plan 10x proposes, and the savings are then measured for each pattern over time, so the savings can be checked rather than taken on faith. Grepr auto-tunes inside its own cloud and commits to no number, stating that results depend on how noisy your logs are.
Pricing: Grepr charges for compute plus the volume you send, and publishes no rate card. 10x charges a flat fee per node (a node is a machine, host, or pod running a log collector), the price is listed publicly, and it does not rise as your log volume grows.

How does 10x compare to Tero?

What Tero is: a piece of software that sits between your apps and your log tools and screens the log traffic. You write rules that tell it to drop lines, sample them, rate-limit them, or blank out sensitive fields before they reach those tools.

Keeping your data: Tero cuts the amount of log data one way, by deleting lines before they reach your log tool, and what it deletes is gone. 10x can cut the same amount while keeping every line, and it drops or samples only when you choose. It groups your logs into patterns (a pattern is one kind of log line, all the lines that say the same thing with different timestamps and IDs), and for each pattern it picks the cheapest way to keep that line, based on the log tool you use:
Compact (shrink the line where it sits): on Splunk, self-hosted Elasticsearch or OpenSearch, and ClickHouse, 10x shrinks each line to a fraction of its size, and your tool still stores it, searches it, and shows the full original line.
Tier down (move the line to a cheaper storage class): when your tool sells a lower-cost storage class you can still search, like Datadog Flex or CloudWatch Infrequent Access, 10x moves the line into it.
Offload (park the line in storage you own): with any tool, 10x sends the line to an S3 bucket (cheap cloud storage) in your own account. When you need those lines again, you fetch the exact originals back instantly, with no slow restore step and nothing loaded back into your log tool.
No way back with Tero: Tero keeps no copy, so nothing it deletes can be brought back.
Setup and upkeep: with Tero you write reduction rules for each source, and someone revises them whenever a log's format changes. 10x needs no per-source rules: it decides what to do with each pattern by itself, and you set a budget for your log spend and approve the plan it proposes.
Pricing: Tero publishes no price; you book an assessment and a sales engineer gives you a number. 10x's price is published and charged per node (a node is a machine, host, or pod running a log collector), and it depends on how many nodes you have, not on how much log data you send.