The short answer

Kleido is built on industry-standard locksmith references, cross-checked against real-world cuts performed by a working automotive locksmith on the team, and continuously refined by reports from locksmiths who use the data in the field every day.

Where the data comes from

Each series record (code prefix and range, key blank cross-references, Lishi tool matches, key profile geometry, cut count, and depth/space values) is built from the same authoritative references the trade has used for decades, then cross-checked against real key cuts and lock decodes done by a working automotive locksmith. The result is a record that matches what you'd cut on the bench, not a copy-paste of one source.

The correction loop

When a locksmith in the field finds a code that doesn't cut correctly, that's a signal we take seriously. Email contact@kleido.app with the series, the code, and what was wrong, and the record is re-checked against reference sources within 1-2 business days. Corrected series get a fresh dated stamp on their page. Code accuracy isn't a one-time import. It's a moving target maintained by feedback from working locksmiths.

Who runs it

Kleido is built by a small team with a working automotive locksmith on the data side and an engineering background on the software side. Every feature in the product comes from real cuts on real keys. The team uses the same Lishi tools, key blanks, and code lookups that any working automotive locksmith uses. The difference is the data gets cross-checked, dated, and corrected the moment the field reports a miss.

Coverage and scope

Kleido covers roughly 3,700 automotive vehicle series with more than 1.6 million bitting codes. Every series carries make, model, year range, code prefix, code series range, cut count, key profile geometry, and (where available) Lishi tool matches. Sub-models are tracked separately when their key system differs. The public sitemap reflects the current published catalog.