Billions of transactions, two-thirds lower cost: Why ProcessOut switched from Elasticsearch to ClickHouse Cloud

T1Covered by 1 source · first reported by Databricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale at 30 Sept 2025, 00:00 UTC

ProcessOut replaced a costly, slow, hard-to-change Elasticsearch setup with ClickHouse Cloud, lowering costs by two-thirds and reducing latency from minutes to ~2 seconds.

Sources

• T1Billions of transactions, two-thirds lower cost: Why ProcessOut switched from Elasticsearch to ClickHouse CloudDatabricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale30 Sept 2025, 00:00