Pricing
Your bill is a function of what you forward. So change what you forward.
Auditty is licensed on the volume it ingests and quoted in annual tiers, because volume is what the saving is made of. What we can show you now, honestly, is the part of your bill that is under your control today.
Typical deployments settle between 3% and 10%. Everything not forwarded is still written to your bucket in full.
Defaults to S3 Standard list price. Lower it if you are on Nearline, Infrequent Access or a committed discount.
Ingest cost today
$91,250/yr
500 GB/day × 365 × $1
With Auditty
$10,855/yr
- Forwarded · 25 GB/day
- $4,563
- Vault · 22,800 GB stored
- $6,293
Bill reduction · before licensing
$80,395/yr
88% less on ingest and storage, while keeping 100% of the raw data queryable.
Auditty's licence is not included above. It is quoted in annual tiers against the volume we ingest. If you have a quote from us, put it in and this becomes your net position.
Nothing is prefilled, because we do not publish a rate. Leave it empty and the figure above is the reduction before licensing.
Object storage is billed by your cloud provider directly. We never hold your data or your credentials, so there is no egress or storage margin in between.
What the licence includes
Unlimited rules and fingerprints
Pattern volume is not a billing lever. Cardinality is the problem you came here to solve.
Unlimited backfills
Pulling your own data out of your own bucket is not a metered event.
Every forwarder
File, object storage, and your existing SIEM or log vendor. No connector tiers.
The whole control plane
Dashboards, insights, fleet rules and convergence views. Node count is not a billing lever, so scaling the fleet out costs nothing to watch.
Alternatives
This is not the only way to cut a log bill.
Some of the other ways are cheaper than us, and one of them you already own. Worth knowing which situation you are in before you get a quote from anyone, including from us.
If the waste is a handful of known patterns, your current vendor's own exclusion filters will deal with it for free and you should go and do that instead. If most of your logs are not Kubernetes container output, a general-purpose pipeline fits better than we do. We wrote the comparisons ourselves, so treat them accordingly, but every claim about another product is a quote from their own documentation with a link to it, and each one has a section saying plainly when they are the better buy.
Auditty vs Grepr
Grepr is a hop in your log path. Auditty is not in the path at all.
Auditty vs Cribl
Cribl reduces what you tell it to. Auditty decides, and you override it.
Auditty vs Edge Delta
Edge Delta wants to be your observability platform. Auditty wants to lower its bill.
Auditty vs Datadog’s own log cost controls
Exclusion filters move the indexing line. They do not move the ingestion line.
Questions
On cost and commitment.
How is Auditty priced?
Auditty is licensed on ingested volume, meaning the bytes the agent reads on the node, and quoted in annual tiers so the rate falls as volume rises. We meter what we read rather than what we forward, so tightening your rules cuts your log vendor bill without changing what you pay us.
Node count, pattern volume, rule count, retrieval count and forwarder types are not billing levers, because high cardinality is the problem customers arrive with and metering it would penalise them for it.
Object storage is billed by your cloud provider directly to you. Auditty never holds your data, so there is no storage or egress margin in between.
How much can Auditty actually save me?
Savings depend on how repetitive your logs are, and most production log volume is highly repetitive. Deployments typically settle at forwarding between 3% and 10% of ingested volume, with the remainder summarised and archived.
As an illustration, at 500 GB per day and a $0.50 per GB ingest rate, forwarding 5% reduces annual ingest cost from roughly $91,000 to roughly $4,600, with about $6,300 per year of object storage to retain a full year of the raw data in compressed form. The calculator on the pricing page lets you substitute your own volume and rates.
Those figures are the change to your ingest and storage bill. They do not include Auditty’s own licence, which is quoted in annual tiers against ingested volume. Your net position is that reduction minus the quote.
Does Auditty replace Datadog, Splunk or my existing SIEM?
No. Auditty sits upstream of your existing log vendor and reduces what reaches it. You keep your dashboards, alerts, queries and runbooks; they simply operate on a stream that no longer contains the repetitive lines nobody reads.
This is deliberate: replacing an observability stack is a multi-quarter migration, while reducing what you send it is a Helm install. Auditty forwards to file destinations, object storage and existing SIEM or log vendors, with no per-connector licensing.
Does Auditty stop working if it cannot reach your servers?
No. Auditty entitlements are cryptographically signed tokens verified locally on the node, so there is no phone-home licence check that can disable your log pipeline when Auditty's service has an outage.
Nodes that lose contact with the control plane continue processing with their last validated rule set and keep writing to your object storage. Loss of the control plane costs you visibility and rule changes, not log processing.
Where is my log data stored, and for how long?
Your log data is stored in your own Amazon S3, Google Cloud Storage or Azure Blob Storage bucket, under a prefix you choose, compressed and partitioned by time in an open format your own tools can read. Auditty never holds a copy.
Retention is whatever your own bucket lifecycle policy says, because it is your storage and your billing relationship. Auditty applies no retention limit and takes no storage margin.