Public repository and README only. No ChronDB process or client workload was run by Toolglass.
TESTED BY TOOLGLASS: NO
What is it?
ChronDB is a key/value database organised around chronological history and branching. The pitch is simple to state and difficult to make useful: ask not only what a value is, but what it used to be.
Why did Radar notice it?
Most teams bolt an audit trail onto a database after the fact. ChronDB treats history as the starting point. That makes it an unusually clear experiment in whether familiar database access can coexist with a versioned model underneath.
What's the catch?
A protocol name is not feature parity. Transactions, restart recovery, query coverage and operational cost still need to be measured against the application you actually have.
Radar verdict
A genuinely odd database idea that deserves a careful client-compatibility test before anyone calls it a replacement.
Next step
Define a tiny workload, then test historical reads, branching and restart recovery.