Customer stories · Financial technology

How Eltropy Optimized Infrastructure with Kloudfuse Observability

Eltropy, a leading communication platform for Community Financial Institutions, transitioned to Kloudfuse to tackle escalating costs, unsustainable data growth, and reactive troubleshooting. This transition led to significant improvements in cost management, operational efficiency, and service reliability.

The outcomes include

100xCost control despite a 100x increase in data
92%Reduction in debugging time
99.99%Enhanced service availability

About Eltropy

Eltropy is the leading digital conversations platform that uses AI to help community financial institutions (CFIs) communicate and engage with their customers and members. Eltropy’s platform integrates multiple communication channels, including text, SMS, chat, video, and voice, into a single system. This allows CFIs to automate and improve their operations, increase productivity, and build relationships with their local communities.

Kloudfuse has been a game-changer for Eltropy. Despite a 100X increase in data volume, we’ve managed to keep costs steady. The unified platform has simplified our observability and slashed our debugging time by 92%, transforming our approach to product reliability from reactive to proactive.

Challenges

Historically, Eltropy relied on three separate platforms for Observability — New Relic for tracing, Elastic for logs, and CloudWatch for infrastructure monitoring — each contributing to escalating costs as data volume increased. As Eltropy’s services expanded, the complexity and volume of data grew, leading to several challenges:

  1. Rising Costs

    The cost of observability data, particularly logs, was escalating due to the increasing data volume and the maintenance of three separate monitoring platforms. Additionally, existing solutions charged premium fees for data storage and archival. Eltropy also incurred extra costs for transferring data over the network to these SaaS observability platforms.

  2. Sustainability Concerns

    The company’s rapid growth and the rising trend towards voice communication (expected to account for 95% of interactions) projected a 20-fold increase in data volume, making their existing solutions unsustainable.

  3. Reactive Troubleshooting

    Eltropy relied primarily on logs for debugging, which led to a reactive approach by addressing problems only after they happened. This affected their service level agreements (SLAs).

Solution: Transition to Kloudfuse

Recognizing the need for a more scalable and cost-effective solution, Eltropy transitioned to Kloudfuse. Several key factors made Kloudfuse the ideal choice:

  1. Unified Platform

    Kloudfuse offers a consolidated view of observability data across logs, tracing, and metrics, simplifying monitoring and management.

  2. Predictable Costs

    Kloudfuse’s VPC deployment model provides a cost-effective and predictable pricing structure that does not rise with data volume. By managing their own observability solution, Eltropy also avoids additional egress data transfer fees typically incurred when sending data to SaaS vendors. Furthermore, Eltropy benefits from lower storage costs with AWS compared to the premium storage charges of SaaS providers.

  3. Compatibility with OTEL

    Kloudfuse’s support for OTEL mitigates the risks associated with vendor lock-in. If needed, Eltropy can switch vendors without extensive re-instrumentation.

  4. Data Control and Compliance

    Hosting data with Kloudfuse’s VPC deployment ensures compliance with data security and privacy requirements, crucial for the financial services sector.

  5. Expert Support

    Kloudfuse’s support and subject matter expertise during the evaluation phase further solidified Eltropy’s decision to adopt Kloudfuse.

Benefits

Post-transition, Eltropy experienced several key benefits:

  1. Cost Management Despite Volume Increase

    Despite the 100-fold increase in data volume, Eltropy’s costs remained the same. Kloudfuse’s predictable, license-based pricing model also effectively safeguards against future cost spikes.

  2. Simplified Engineering

    Kloudfuse enabled Eltropy to integrate logs, tracing, and metrics into a unified observability stream (MELT), featuring customized alerts and dashboards for effective issue tracking and resolution. This enhancement improved debugging efficiency, reducing resolution time from one hour with two engineers to under 10 minutes with one engineer, resulting in approximately 92% time savings.

  3. Improved SLAs

    The unified platform and advanced alerting system enabled Eltropy to transition from reactive to proactive operations. This change improved uptime from 99.95% to 99.99%, significantly enhancing customer satisfaction.

Kloudfuse has transformed our approach to observability and operations. By consolidating our observability across metrics, logs, and traces into a single, unified platform, we’ve achieved 99.99% service availability and gained remarkable control over both our data and costs.

Current State and Future Plans

Eltropy’s transition of Kloudfuse has been transformative, effectively addressing cost, scalability, and operational challenges. The switch has not only kept their budget on track despite growing data volumes and added capabilities across the entire observability stream (MELT) but has also enhanced their operational efficiency and customer satisfaction.

Eltropy, now utilizing Kloudfuse across operations, DevOps, and development teams, plans to collaborate further with Kloudfuse to implement additional functionalities such as product analytics, continuous profiling, and real user monitoring.


More customer stories.

Bring an incident. We'll bring the platform.

Run Kloudfuse against your own telemetry, in your own cloud, and see what a single correlated view does to your mean time to resolution.