Flat monthly pricing by daily throughput.
Last updated April 30, 2026
| Plan detail | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|
| Daily limit | Up to 2 TB/day | Up to 5 TB/day | Up to 10 TB/day | 10 TB+/day |
| Capacity model | Shared capacity | Shared capacity | Shared capacity | Dedicated regional capacity |
| Limit measured by | Ingress or egress, whichever is reached first | Ingress or egress, whichever is reached first | Ingress or egress, whichever is reached first | Ingress only. Unlimited egress. |
| Destinations | ||||
| Datadog | ||||
| S3 | ||||
| Trimming | ||||
| Log filters | ||||
| Sampling | ||||
| PII masking | ||||
| Deduplication | ||||
| Log-to-metric conversion | ||||
| Enterprise | ||||
| SAML SSO | ||||
| Immutable audit logs | ||||
| SLA terms | ||||
| Priority onboarding and support | ||||
| Monthly price | $299/mo | $599/mo | $999/mo | Custom |
Ingress
Raw logs received by LogTrim before filtering, sampling, deduplication, log-to-metric conversion, or routing.
Egress
Data sent from LogTrim to destinations such as Datadog or S3.
Why both matter
Efficient pipelines reduce egress, while archive-heavy configurations consume more daily capacity.
Drop low-value events upstream so they never become billable Datadog ingestion volume.
Send raw logs to cheaper long-term storage while forwarding only high-signal data to Datadog.
Turn high-volume success patterns into request counts, rates, and latency metrics instead of raw indexed logs.
Keep representative logs for noisy success traffic while preserving complete errors, warnings, and anomalies.
Collapse repeated events into one representative log with a count, first-seen time, and last-seen time.
Remove unused fields and oversized attributes before forwarding logs to expensive indexed storage.
Shared-capacity tiers apply daily ingress and egress limits to preserve performance for all tenants. Organizations with sustained usage above 10 TB/day should move to enterprise.
Enterprise customers receive dedicated regional capacity, negotiated burst limits, SAML SSO, immutable audit logs, SLA terms, priority onboarding, and full S3 archival defaults.
Refund conditions are defined in the Refund Policy. Additional legal controls are defined in the Terms and Conditions and Privacy Policy.
Do the priced plans differ by features?
No. Starter, Growth, and Scale include the same reduction engine; each tier increases daily throughput.
How are shared-plan limits measured?
Shared-capacity limits are measured against ingress or egress, whichever is reached first. Ingress is data received by LogTrim; egress is data sent to destinations such as Datadog or S3.
Do S3 archives count toward my daily limit?
Yes. S3 routing uses egress capacity, so archive-heavy configurations consume plan capacity faster than metric-heavy or Datadog-only configurations.
Can I reduce egress usage?
Yes. Log-to-metric conversion, sampling, deduplication, payload trimming, and per-destination routing reduce how much data leaves LogTrim.
What changes with enterprise?
Enterprise includes 10 TB+/day negotiated capacity, dedicated regional infrastructure, SAML SSO, immutable audit logs, SLA terms, priority onboarding, and support.
Are subscriptions billed in advance?
Yes. Monthly subscriptions are billed in advance and auto-renew unless canceled before the next renewal date.