Any Volume
Predictable Price

Reduce Splunk, Datadog, and Elastic costs by 50-80%

No GB Limits

No GB Limits

No per-GB charges.
Same price at any volume

Node Based

Node Based

Price scales with nodes.
Not with log volume

All Included

BYO Stack

Works with your tools.
Cut your costs

Simple Pricing

One question: How many nodes run log collection?

Monthly
Annual Save 17%
Tier Nodes Annual Price
Starter up to 50 $15,000
Pro up to 150 $25,000
Growth up to 300 $35,000
Scale up to 500 $50,000
Business up to 750 $65,000
Business+ up to 1,000 $80,000
Enterprise up to 1,500 $105,000
Enterprise+ 1,500+ Contact us

All tiers include unlimited log volume, all products, and all features.

Calculate ROI

Preview compound savings for your log analytics platform

1 1500+
$

Your actual monthly bill from your vendor

Estimated Annual Savings
$318,000/yr
Splunk $600,000/yr → With Log10x $282,000/yr

What's Included ?

Filter noisy events (30%), optimize the rest (40%). Combined 58% reduction before shipping. Learn more
Cost Breakdown (Monthly):
Current Vendor Cost: $0
New Vendor Cost: $0
Log10x Cost: $0
Total New Cost: $0
Annual Savings
$90,000
75% total savings
Monthly Savings
$7,500
per month
Log10x Price
$2,500
per month
Book a Demo
For Storage Streamer-specific savings, see Storage Streamer Calculator
Calculate savings from your actual logs with the Dev CLI

What's Included

Every tier includes all products and all capacity. No per-GB charges from Log10x.

All Products

Cloud Reporter
Edge Reporter
Edge Regulator
Edge Optimizer
Storage Streamer

Unlimited

Log volume
Surge capacity
Applications
Environments
Destinations

Never Charged

Per-GB ingestion
Per-GB storage
Per-query fees
Overage charges
Hidden fees

Frequently Asked Questions

Pricing Model

How does node-based pricing work?

A node = any host running a Log10x collector, regardless of instance size:

  • Kubernetes: 1 worker node = 1 billing unit (DaemonSet deployment)
  • VMs / bare metal: 1 host running a collector = 1 billing unit
  • ECS: 1 container instance = 1 billing unit

Instance size (vCPU, memory) does not affect count. One question determines your tier: "How many nodes run log collection?"

Everything else is unlimited — log volume, traffic spikes, applications, environments, and destinations. No per-GB charges from Log10x.

How does this compare to volume-based pricing?

Volume-based tools charge per GB ingested, processed, or stored. Log10x charges per node.

When your traffic grows, their bill grows proportionally. With node-based pricing, cost stays flat as log volume increases.

Log10x pricing is based on infrastructure capacity (node count), not log volume. Your bill is the same whether you process 1 TB/day or 100 TB/day.

What savings can I expect?

Savings depend on which apps you deploy, your daily log volume, per-GB ingestion cost, and how much you divert to S3:

  • Edge Optimizer — cut storage and analytics costs 50%+ by forwarding compact events
  • Edge Regulator — cost-based sampling of noisy event types
  • Storage Streamer — store in S3 Standard at $0.023/GB, stream to your SIEM on demand

Use the ROI Calculator above with your actual numbers for a personalized estimate.

Is volume unlimited?

Yes. Whether you process 1TB/day or 100TB/day, your price is determined only by node count.

Your bill stays the same regardless of log volume. We never charge per-GB for ingestion, processing, storage, or queries.

What if my log volume doubles?

Your price doesn't change.

Log10x pricing is based on infrastructure capacity (nodes), not log volume. If you double your traffic but keep the same node count, your bill stays identical.

What about autoscaling?

Your tier is based on P90 baseline node count over 30 days. Transient spikes from autoscaling or traffic surges don't affect your tier.

Spot instances, preemptible nodes, and ephemeral nodes that exist only during scale-up events are not counted.

If your cluster scales from 100 to 300 nodes during a traffic spike but stays at 100 nodes 90% of the time, your billing count is 100.

What if I exceed my tier?

We notify you at 75%, 90%, and 100% of tier capacity. You get a 14-day grace period to upgrade. No surprise charges.

The Console shows your current usage in real-time. Upgrade is one-click and manual — we don't auto-charge.

Your tier is based on P90 baseline, so temporary spikes don't trigger notifications.

Architecture

How do I know how many nodes I have?

For Kubernetes, run kubectl get nodes to see your worker node count.

For other architectures, count the hosts/VMs running your log collector (Fluentd, Fluent Bit, Filebeat, OTel Collector, Logstash).

The billing unit is collector instances, which equals node count for DaemonSet deployments — the most common pattern.

Do pods count separately from nodes?

No. Kubernetes worker nodes count. Pods running on those nodes don't add to your count.

Example: If you have 100 worker nodes running 1,000 application pods, your node count is 100 — not 1,100.

What if I only use Storage Streamer (no Edge)?

Count the collectors shipping logs to S3. Those are your billing units. See Storage Streamer for details.

What if I only use Cloud Reporter (no Edge)?

Count concurrent 10x Engine instances sampling your log analytics platform. Each running instance (Lambda function, k8s CronJob) counts as one node. See Cloud Reporter for details.

If you also use Edge, Cloud Reporter doesn't add to your count — only Edge collectors are billed.

What if I use both Edge and Storage Streamer?

Count your Edge collectors only. Cloud products don't add to node count.

If you run 10x Edge on 200 nodes and also use Storage Streamer, you pay for 200 nodes. Storage Streamer and Cloud Reporter are included at no extra charge.

Do analytics servers (Splunk, Elasticsearch, Datadog) count?

No. Only hosts running a Log10x collector count. Your analytics infrastructure — Splunk indexers, Elasticsearch data nodes, Datadog Agent hosts — are not billing units.

Example: 200 EKS worker nodes running Filebeat DaemonSets + 30 Elasticsearch data nodes + 3 Splunk indexers = 200 nodes. Only the worker nodes running log collection count.

Do Lambda functions count as nodes?

Yes. Each concurrent Lambda invocation running the 10x Engine counts as one node — the same way edge forwarder pods and S3 uploaders count. Lambda functions are shippers like any other.

Your tier is based on P90 baseline concurrent invocations over 30 days. Short-lived spikes from autoscaling don't affect your tier.

What if I deploy only to a subset of nodes?

Count only the nodes running the Log10x DaemonSet. If you use nodeSelector or nodeAffinity to deploy on 50 of your 200 worker nodes, your count is 50.

What are the CPU and memory requirements per node?

You control both. The 10x Engine runs on the JVM, so memory (-Xmx) and CPU (thread count) are set explicitly in your DaemonSet manifest.

512 MB heap + 2 threads handles 100+ GB/day per node. See the resource requirements FAQ for sizing details and benchmarks.

Getting Started

Which products are included?

All of them. Every tier includes:

Every tier includes every product.

Is there a limit on applications or environments?

No limits.

You can run unlimited applications across unlimited environments (dev, staging, prod, etc.). You pay only for collector nodes, regardless of how many apps or environments you monitor.

Can I upgrade or downgrade?

Yes. One-click upgrade in the Console with pro-rated billing.

Downgrades are available at the end of your billing cycle.

Is there a free trial?

Yes — two ways to start:

  1. Dev (free, no account) — download and run on your own log files locally. See your reduction ratio in minutes.
  2. 14-day trial (full platform) — credit card required. Cancel from the Console at any point during the trial and you won't be charged.

After the trial, your account converts to the tier matching your node count. If you don't select a plan, access stops — no automatic charges.

Support

What support is included?

Every plan includes full support — no paid tiers or add-ons:

  • Dedicated Slack channel per customer for direct access to the engineering team
  • Business-hours support with next-business-day response
  • P1 incidents (production pipeline down): 4-hour response
Do you offer custom SLAs?

Yes. For teams that need guaranteed response times, 24/7 coverage, or uptime commitments, we offer custom SLA agreements.

Contact us to discuss terms that match your requirements.

Security & Billing

Where does my log data go?

Nowhere outside your infrastructure. The 10x Engine runs as a sidecar or pod inside your cluster. Log data is processed in-memory and forwarded to your existing destinations.

No log data is sent to Log10x servers. The only outbound connection is lightweight telemetry used for billing and the Console dashboard. See Metrics API for the complete list of what is sent, or Security & Compliance for more details.

Annual vs monthly billing?

Both available. The pricing table above shows both — toggle between annual and monthly.

Annual plans are billed upfront for the year. Monthly plans are billed at the start of each month. No long-term contracts on either option.

Is there a minimum commitment?

No. The smallest tier (Starter) covers up to 50 nodes. Monthly plans can be cancelled at the end of any billing cycle.

Can I use Cloud Reporter or Storage Streamer standalone?

Yes. Both work independently. You don't need Edge apps to use Cloud Reporter or Storage Streamer.

Pricing is the same — based on the number of collector instances running. See the Architecture FAQ items above for counting details.

Have more questions?

Explore our FAQ for more detailed answers.

Read the Full FAQ

See Your Savings in 14 Days

14-day trial. All products included. Cancel anytime.

Try For Yourself Book a Demo