we are sharing how we built CobbleDB, our replacement for AWS DynamoDB that powers key-value storage for our web-scale search engine.
we optimized CobbleDB for our exact read and write patterns. result: 5x lower batch read latency and at least 20% lower serving cost (in practice much higher).
what i'm most excited about is how it was built and deployed: 2 human engineers plus our internal system that runs a swarm of hundreds of persistent AI agents in an autonomous loop. the agents reviewed code and infra changes, caught blockers that were easy to miss, prepared fixes, tests, and monitoring, ran the migrations, and did head-to-head comparisons on real traffic to hunt down bugs and inefficiencies. they tracked CI and rollout gates and kept project readouts up to date. production actions stayed explicitly human-owned though.
more details and some insights about our search engine in the blog:
if you want to work on problems like this, DM me or apply at
We’re publishing research on how we built CobbleDB, our key-value database that serves web content for Perplexity search.
Two engineers and a team of hundreds of proactive, always-on AI agents built the core infrastructure in two months.