Grepr Cost Savings Case Study

Jad Naous
June 6, 2025

Goldsky is Web3’s Realtime Data Platform, enabling developers to build powerful dApps faster with high-performance blockchain indexing, instant subgraphs, and custom data streaming pipelines. The team reached out to us 6 months ago asking for help in managing log volumes and reducing costs, because they were feeling that the value they were receiving from collecting and storing so many logs was not aligned to the spend. Grepr was deployed soon after, and we were able to reduce their Datadog logging bills by 96%.

Paymahn Moghadasian, Lead Engineer at Goldsky, was responsible for the deployment.

Deployment 

Goldsky uses Terraform internally to manage their infrastructure. They have separate staging and production environments. The Datadog agents in those environments are also managed via Terraform.

Paymahn created a pipeline and then pointed the Datadog agents for staging to Grepr within 20 minutes, and Grepr got to work. The volume was minimal, about 8 messages/second, but even with this, Grepr was getting about 80% reduction.

Paymahn left Grepr working for about a week to gain confidence, and then decided to roll out to production. Here, the situation was different because we want to minimize risk. For the prod rollout, Paymahn used Datadog’s ability to dual-ship logs, adding Grepr as a destination while continuing to send logs to Datadog at the same time. Here are the steps he took:

  1. Enable dual shipping in Datadog for logs (https://docs.datadoghq.com/agent/configuration/dual-shipping)
  2. For each service: Add a filter in Grepr to drop all logs except the service you want to migrate.
  3. Once logs for that service are passing through Grepr correctly and being received by Datadog, add a Drop Rule to drop logs for that service not coming from Grepr.
  4. Tune set up to add exceptions if needed so as not to modify existing alerts or dashboards.
  5. Run for one day to validate everything is working as expected.
  6. Repeat for the next service
  7. Optionally update some alerts or dashboards to increase reduction and use summarized data instead of raw data.
  8. Run for two weeks to validate. Turn off dual-shipping from the agents.

The whole process took 4 weeks, end-to-end.

Cost savings

For May 2025:

  • Indexed Logs: 5.7 billion messages reduced to 250 million messages = ~96% reduction
  • Ingested Logs: 12 Terabytes of logs reduced to 795 Gigabytes = ~93% reduction

Dollar savings on Goldsky’s bill were commensurate. When combined with Grepr’s costs, Goldsky was able to save over 85% of their logging spend on Datadog.

Impact on MTTR

Two words from Paymahn: “no impact”. In fact, they reported that the reduction in noise made the logs easier to read through and understand than before Grepr. 

Other benefits

  • Get time back: by tackling log costs quickly and decisively with Grepr, Goldsky was able to get back time for building their product.
  • Historical searches with no rehydrations: they were able to search through logs over multiple months without having to rehydrate them and pay an additional cost.
  • Readable logs: when noise is filtered out, it’s easier to read the logs.

In Paymahn’s words:

  1. Grepr’s immediate, high-touch, white-glove support was excellent. We always felt taken care of.
  2. The Grepr UI was good for our needs. Definitely not competitive with Datadog’s UI, but that’s not the point.
  3. Grepr’s was always up and available for us.
  4. Logs arrived at Datadog with some minimal added latency, but not enough to actually matter in any meaningful sense.

Paymahn’s final comment, “Grepr allowed us to not substantially change any of our established observability use cases or processes by essentially getting rid of the noise in the data. It's the best of both worlds, lower costs without any retraining!”

Share this post

More blog posts

All blog posts
Product

All Observability Data Is Equal But Some Is More Equal Than Others

With apologies to George Orwell. Not all Observability data is salient all the time, some data is required all the time but most data is only germane when investigating an issue.
June 24, 2025
Product

Grepr vs Vector

Vector and Grepr both function as observability data pipelines, but they differ sharply in complexity and automation. Vector, an open-source tool sponsored by Datadog, is powerful and flexible but requires extensive manual configuration, domain-specific scripting (VRL), and careful infrastructure planning. In contrast, Grepr is a fully automated, AI-driven observability platform that dynamically manages thousands of data transformations without requiring custom coding. It reduces observability costs by up to 90%, stores all data in queryable formats like Apache Iceberg on AWS S3, and integrates seamlessly with tools like Datadog and Splunk. With Grepr, organizations can deploy in minutes instead of days—without the operational overhead.
June 20, 2025
Product

100% Insight With 10% Of Your Data

Modern web applications are rich, dynamic, and heavily reliant on frontend frameworks like React and Vue, which makes browser-side logging essential for understanding both code execution and user behavior. The Datadog browser logs SDK allows developers to collect this data, but with high traffic, logging can become expensive due to Datadog’s volume-based pricing. Grepr solves this by acting as an intelligent intermediary: it receives all logs, stores them cost-effectively, and uses AI-powered filtering to reduce the volume sent to Datadog by 90%—without dropping any data. It aggregates and summarizes repetitive logs, maintains full fidelity through semantic understanding, and even retains query access to all original data via a dashboard using the same syntax as Datadog. This approach allows developers to maintain 100% insight with only 10% of the data volume and cost, enabling full visibility into user behavior and app performance without budget concerns.
June 17, 2025

Get started free and see Grepr in action in 20 minutes.