Just wrapped up a post-mortem on an OpenClaw rollout. The initial "per-query" pricing seemed clean. Then the bills hit. Here's where the real costs live for a ~50 engineer, 10 service SaaS shop.
The base model is `$0.12/1k queries`. Simple. But they define a "query" as any `SELECT`, `INSERT`, or `UPDATE` sent to their query engine. Our application's health checks? Those are `SELECT 1`. That's ~4 million "queries" a month right there, just for the pods to stay alive.
```yaml
# Example 'optimization' we had to implement
# Original health check (cost us ~$500/month):
# readinessProbe:
# exec:
# command: ["/bin/sh", "-c", "openclaw-client --execute 'SELECT 1'"]
# New health check (cost: $0):
readinessProbe:
exec:
command: ["/bin/sh", "-c", "pg_isready -h localhost"]
```
Then there's the "data hydration" fee. If your queried data hasn't been accessed in 30 days, they "rehydrate" it from cold storage. That's `$0.85/GB`. Our monthly historical report? Suddenly a $200 line item for data we already store ourselves.
The real kicker is the "concurrent analysis session" license. Every dashboard user **and** every internal admin panel using OpenClaw counts as a "session." Our 5-person data team has licenses, but so does the customer-facing analytics page. That's `$45/user/month` scaling with your customer base, not your team size. Sneaky.
Moral of the story: Their pricing is a distributed system. Failure modes (costs) emerge at scale.
Your breakdown of the health check costs resonates. We found the same issue with our distributed tracing vendor, where each span export was a "transaction." Our CI/CD pipeline's integration tests were generating millions of dummy spans, creating a massive phantom bill. The per-query model inherently punishes high-cardinality, low-value operations.
Regarding the "data hydration" fee, have you validated their 30-day inactivity claim? We instrumented our own audit logs and found they were charging for rehydration on datasets accessed within a 7-day window. It required a lengthy support ticket with our own timestamp evidence to get credits.
The session licensing model you mentioned is the true scaling killer. It often transforms a predictable variable cost into a chaotic, user-count-dependent fixed cost. Did your finance team model the per-employee cost impact for internal tools? Ours missed it entirely.
—chris