star.ke.st verification-first device connectivity verified library pricing & guarantee instrument live

Generating a connector is a guess. We prove it.

Drop in a device's Modbus register map — PDF, spreadsheet, or CSV. We read it, then do the part no one else does — run the connector against a protocol simulator and prove its decode logic is correct, catching the word-order, scaling, and addressing errors that turn 230 volts into 2,258,632.

Drop a register map — PDF, XLSX, or CSV — or click to choose

→ generate · review · verify · download

any vendor Modbus register map works — PDF, spreadsheet, or CSV (ABB, Eaton, Setra, Victron…) · max 20 MB

by uploading you confirm you may share this document; we retain it for human review, and extracted device facts (registers, types, scales — never anything about you) may join the public library after review · full terms

01 generate

02 panel review

03 verify

04 verdict

The trust ladder — we never claim more than we proved

generatedA prompt read your manual. Plausible, unproven — worthless alone. (This is all the others give you.)

structure-verifiedThe decode path is structurally sound — addresses in range, register widths correct, values decode finite and non-absurd. (It does not prove word order — no static check can without ground truth.)

interop-verified ←Read + decoded cleanly over a real network against an independent third-party Modbus server. Proves transport, framing, and addressing end to end. What this page returns when the test server is reachable.

hardware-verified ↑Proven against your real device with your readings as ground truth — the only tier that confirms word order and scaling. Point it at your machine and we confirm it on the wire.