Cut Log
Costs 50-80%
Automatic · BYO stack · Zero egressSplunk · Elasticsearch · Datadog · CloudWatch
Optimize Everywhere
The 10x Engine runs where your logs are.Choose from included apps, compound savings
Dev
Preview savings
Analytics
Pinpoint waste
Edge
Enforce budget
Storage
Ingest on-demand
10x Engine
Traditional pipelines parse every event individually.10x compiles log structures once, applies them billions of times

AOT Compiler
Map log event structures from repos, containers, and Helm charts. 150+ frameworks included, extend via CI/CD.

JIT Stream Processor
Uses mapped structures to assign a hidden classFrom Chrome V8: log events with identical structure share a pre-compiled class — fields accessed directly, not parsed each time. What are hidden classes? → to events at runtime — no regex or extraction rules to maintain
Frequently Asked Questions
Quick answers to common questions about the 10x Engine
A stream processorA Gartner category for software that processes continuous data streams in real time. Gartner ESP → that analyzes code and binaries to turn log events into typed, class-based objects—not raw text—eliminating 50–80% of log storage and analytics costs.
A lightweight, portable data engine that runs where your data is—locally, at the edge, or in the cloud. Works with your existing infrastructure—analytics, forwarders, and storage.
Product overview — architecture, deployment models, and integrations. Read more →
Pipeline tools — Cribl, Logstash, OTel Collector, Vector — require regex, grok, VRL, or OTTL rules for every log format. Those rules break when code changes and need dedicated pipeline engineering to maintain.
10x takes a different approach. The AOT compiler builds symbol vocabulary from repos and containers. At runtime, the stream processor uses those symbols to recognize log structure and assign cached hidden classesInspired by Chrome V8: objects with the same shape share a class, enabling direct field access without JSON parsing or regex matching. What are hidden classes? → to each event — no regex, no grok, no per-format rules.
Optimize everywhere — The hybrid AOT/JIT engine powers automatic log data optimization at every stage of the pipeline. Test locally, report on costs and regulate billing spikes at the edge, losslessly compact before shipping, ingest from S3 on-demand.
BYO stack — Works with your existing log forwarders, analyzers, time-series databases, object storage, and compute (K8s, Lambda, EC2). No migration required.
Zero egress — The engine runs as a lightweight runtime inside your infrastructure. Log data never leaves your environment. No vendor access to your logs required.
This design cuts log costs 50–80% — securely, without replacing your existing tools.
The 10x Engine — AOT/JIT compilation, hidden classes, and runtime processing. Read more →
Pricing is based on infrastructure capacity—the number of nodes running log collection—not data volume. Log volume spikes, traffic surges, and new applications have no impact on cost.
Tiers, node counting, and what’s included. See pricing →
The 10x Engine is designed to fit your existing infrastructure. A modular extension framework supports easy integration across your stack:
- Log forwarders — Fluentd, Fluent Bit, OTel, Filebeat, Logstash, Splunk UF
- Log analyzers — Splunk, Datadog, Elastic, CloudWatch
- Time-series — Prometheus, Datadog, Grafana, SignalFx
- Object storage — S3, Azure Blobs, GCS
- Compute — K8s, Lambda, EC2, Docker
The 10x Engine runs inside your infrastructure at every stage of the pipeline — locally, at the edge, and in the cloud. No log data is sent to external services. No AI models are trained on your logs. No vendor access to your data is required.
Cut Your Log Costs
Works with your stack. Fixed per-instance pricing


