I am building https://scratchdb.com/ to address this. It's an HTTP wrapper around Clickhouse, and uses pay-as-you-go pricing. It's also open source and easy to host yourself (single go binary.) Currently have users sending in the 1000 requests per second so definitely have capacity.
Typically seeing a 0.1 compression ratio on data before other optimizations.
I'd be really grateful to learn more about what you're looking for (how are you even managing logs today?) Even if you end up not using scratchdb it'll help me figure out the next thing to build!
Typically seeing a 0.1 compression ratio on data before other optimizations.
I have it connected to Fly.io here: https://scratchdb.com/blog/fly-logs-to-clickhouse/
I'd be really grateful to learn more about what you're looking for (how are you even managing logs today?) Even if you end up not using scratchdb it'll help me figure out the next thing to build!