building systems • low performance athlete at @strava
Joined January 2007
- Tweets787
- Following448
- Followers2.3K
- Likes621
Pinned Tweet
Prototyping is cheaper than ever, so I tried to imagine the simplest possible ClickHouse service.
The result is a side project called ClickHamlet. You run:
clickhouse client --host cloud.clickhamlet.com --secure --user <name> --password
And that's it. No sign-up form, real ClickHouse in the cloud.
Jordi Villar retweeted
A pesar del cringe que me doy al ver la charla, he decidido publicarla porque habéis sido siempre TAN majos conmigo que se me ha ido el miedo al posible escarnio público 😂
El link: vimeo.com/trgcon/trg26-nuria
Contadme qué os parece!
this is why @ClickHamlet has no sign-up
an agent (or anyone) just runs a query and gets a real clickhouse. you can then claim it at anytime
How much revenue are database companies losing because agents aren’t able to sign up autonomously?
Today, we’re releasing @tryscope_app's first database benchmark.
We tested 18 hosted databases to see which are ready to win that market. We measured which databases agents could use, analyzed where they failed, and identified best practices to fix the blockers.
Across 1,035 sessions, only 16.6% reached a first working result and failed sessions all came from products not being agent friendly.
We tested 20 model-and-agent-tool combinations across harnesses including Claude Code, Codex and Cursor.
The task: start with no account, set up the named database, write a record, and hand over the credentials. An account or API key alone didn’t count.
What we found:
→ @prisma led with an 88.3% success score, followed by @upstash at 63.3%, @neondatabase and @niledatabase at 43.3%, and @ClickHouseDB at 38.3%.
→ 7 of 18 products had zero successful sessions across every agent tested.
→ CAPTCHAs stopped 373 sessions. Bot blocks stopped another 105. Other barriers included rejected agent email domains and OAuth-only flows.
→ 50 of the 172 successful sessions used a working database without creating an account. Letting agents try the product before signing up made a difference.
An agent can arrive knowing exactly which product it wants to use and still never become a user. For developer tools, the path from “use this database” to a working result is part of your conversion funnel.
See the full leaderboard, methodology and session transcripts: tryscope.com/leaderboard/dat…
Special thank you to our partners @AgentMail and @Agentphone for giving us the right tools to run this experiment.
great work by the clickhouse security team turning this around so fast
@ClickHamlet backends were on 26.10.3.7 five minutes after the release
CVE-2026-116366
first CVE on my name just dropped. unauthenticated RCE on any @ClickHouseDB instance using just the public service hostname.
special thanks to San and the ClickHouse security team. the report was accepted within 20 minutes on Bugcrowd.
P.S. Clickhouse Security Team emailed me 1 hour before I reported the vulnerability stating that they "detected attempts of unauthenticated RCE on my instance" which shows how seriously they approach the security of their service in general.
5
758
Jordi Villar retweeted
serverless clickhouse that starts on the first query and stops when idle. no sign-up, real clickhouse, free up to 10 GiB
early preview: clickhamlet.com
moved @ClickHamlet to clickhouse 26.10. quiet upgrade, but a few changes land right where s3 hurts:
- reader refreshes skip GETs for directories that didn't change
- part removal is one batched delete instead of copying each file first
- metadata loads several times faster
the router also caps nested CTE expansion with max_expanded_ast_elements now, before it could grow without limit
4
457
i'm such a good manager i got my grok bots fighting each other, interrupting themselves, and spending more time arguing than doing the actual task
is this AGI, or did they just become a real engineering team?
4
1
523
Jordi Villar retweeted
added stripe billing to @ClickHamlet, first time doing it end to end:
- free and paid plans, checkout + webhooks
- usage meters: compute per GiB-minute, storage per MiB-hour
- costs counted from the moment an account starts paying
- the hour you upgrade is reported once, with idempotency keys on meter events
first customer: me, at 100% off 😅
added stripe billing to @ClickHamlet, first time doing it end to end:
- free and paid plans, checkout + webhooks
- usage meters: compute per GiB-minute, storage per MiB-hour
- costs counted from the moment an account starts paying
- the hour you upgrade is reported once, with idempotency keys on meter events
first customer: me, at 100% off 😅
impossible to escape from ai these days. yesterday, while having dinner, a lawyer and a cinema director were explaining their agents/bots setup..
1
1
294
does it make sense to build a clickhouse offering on top of s3?
last 30 days: $42.34 revenue at our prices, $51.78+ in aws (billing lags ~24h)
if you've run clickhouse on top of s3 you won't be surprised by the puts eating a big chunk of costs: ~410 rows/h inserted turned into ~5,500 PUT/COPY and ~8,000 GET/HEAD an hour, mostly doing merges.
you've to spend hours optimizing, packing small parts and refreshing every 5s instead of 2s did the trick for me
how does ClickHouse Inc make the math work?
3
1
280
no iba a ser menos y Codex no solo ha conseguido hacer que el proyector vaya como un tiro, sino que también ha arreglado el ajuste automático a la pantalla que fallaba más que una escopeta de feria
2
383
I didn't care about deployments when I started working on @ClickHamlet, it was an ugly bash script. Now that it's running for some users, it was time to add zero-downtime deploys:
- releases are immutable and prepared before the switch
- the controller leaves backends running when it exits, the next one adopts them
- a systemd socket unit keeps the ports open while it restarts, so connections queue instead of failing
- routers retry on a fresh connection if their pooled one breaks
- idle and drain timers live as annotations, so they survive the restart
Deployed with queries running, nobody noticed
Your servers start on the first query and stop when you're done, so an idle database runs nothing.
Reads and writes go to separate servers sharing the same storage, so heavy dashboards don't slow down ingestion.
1
216
Your first login creates your service, and you have 2 days to claim it from the dashboard link.
It's in early preview. Try it, break it, and tell me what's missing.
clickhamlet.com
173