SIVARO
Selected work

Every line here is a number that moved.

Filter by the problem you have. Each engagement closed with a benchmarked before and after, measured on the client stack.

6 engagements
Analytics platform Migration

Snowflake to ClickHouse at petabyte scale

The warehouse bill had grown faster than the product. Nobody could map spend to a workload, and the finance review kept getting deferred.

Schema conversion with codec selection, partition strategy taken from real query patterns, and checksum validation on both sides before a single reader moved. Zero downtime cutover.

ClickHouseSnowflakeTerraform
monthly spend
$47K $8.2K
82% lower, verified
Real time analytics Platform build

200K events per second at 12ms P99

Dashboards timed out during customer demos. The team had started building workarounds instead of features.

Kafka ingest partitioned for a 10x spike, MergeTree schemas with ordering keys aligned to the real queries, and TTL tiering so history stopped driving the bill.

KafkaClickHouseKubernetes
p99 query latency
2 to 5s 250ms
10x faster on 200M events a day
API platform Rewrite

Node gateway rewritten in Go

Intermittent timeouts under load, traced to garbage collection pause spikes that only appeared at peak.

Gateway rebuilt in Go with connection pooling and backpressure, benchmarked against production traffic shapes before cutover.

GoKubernetesPostgres
p99 api latency
800ms 12ms
18K rps on one instance, zero pauses
Customer support RAG

Retrieval pipeline that survived launch

Keyword search could not find answers that existed. Escalation rates climbed while the content library kept growing.

Multi stage retrieval with hybrid search, cross encoder re ranking, query rewriting and guardrails, plus embedding drift monitoring after launch.

ClickHouseHybrid searchRe ranking
retrieval accuracy
low recall 99%+
45% lift in support resolution
Infrastructure Right sizing

Over provisioned clusters, no observability

Compute was sized for a peak nobody had measured, and there was no chart putting utilisation next to spend.

Utilisation instrumented first, then autoscaling on request load rather than CPU, with per query cost tracking so the savings stayed after we left.

KubernetesKarpenterTerraform
annual compute
42% waste right sized
about $240K a year returned
Developer tooling GTM

Traffic that never converted

Steady organic traffic on technical terms, almost no inbound. The only offer on the site was a meeting.

Crawl graph and index coverage fixed first, then capture added to the pages carrying real intent, with a free scan replacing the meeting as the first ask.

Crawl graphIndex coverageCapture
orphan pages
17 invisible linked
capture on 11 high intent pages

Illustrative examples while real engagements clear review. Distribution figures come from a sample 142 page scan, not a named client; cost and latency numbers are placeholders until a client signs off.

Want your own before and after?

It starts with the before. The scan measures it in about 40 seconds, free.

P.S. Every engagement on this page started with a measurement somebody was avoiding.