“A single thread cannot make a cord, nor a single tree a forest.”
kordloom.com · FAQ
A Texas software company. We build infrastructure for systems under load, starting with fleet automation. The house style is one Go binary and one database file, self-hostable, with nothing to babysit.
Your install keeps running, because the license verifies offline against keys compiled into the binary and there is no phone-home to fail. Your evidence keeps verifying, because the format is open and the verifier is Apache-2.0. The source outlives the company, because every release attaches its own source tarball and converts to Apache 2.0 two years after it ships.
Vendor-operated services do stop: hosted witness countersignatures, scheduled evidence packs, and support. The vendor review page carries the whole answer, including the part that degrades.
The same three rules.
The mechanism differs by product. The standard does not.
SwitchTender is the product. It runs your fleet from one binary and records every change: who ran what, where, and who approved it. More are coming.
LoomSeal is not a product. It is an open format and a free verifier that ships with the products that need one, so a record can be checked by someone who has never heard of us. It is not sold, has no price, and adopting it needs no permission from us.
LoomSeal is fully open source, spec and verifier both. SwitchTender is source-available and free to self-host and modify. Current license terms live on each product's site.
Never in the proof path. The records, chains, and judgments are deterministic. SwitchTender ships optional advisory AI, off by default, that can only draft text a human reviews. Anything it proposes waits at the same approval gate an operator faces, and the request and decision land in the audit trail.
hello@kordloom.com reaches a human. For the product, switchtender.com starts with the quickstart.