The entity
Veraccord Labs LLC is the legal entity. LockWire Labs is a registered trade name of it, and LockWire™ is its trademark. If you are confirming who you are dealing with — for procurement, for a contract, or for diligence — those three names resolve to one company, registered in Spokane, Washington.
LockWire
LockWire Labs develops LockWire™, a cross-platform security framework written in Rust — cryptography, in-memory secrets, PKI and certificate authorities, ACME, OpenID Connect with passkeys, secure DNS, authenticated time, signed updates, tamper-evident audit, Mesh networking and mail.
The framework includes Saddle, the configuration-driven tool for building, testing, checking and managing the secure development lifecycle of your projects. Saddle’s Rig workflows coordinate testing across authorized machines and devices, with Mesh providing secure connectivity to those hosts.
AI provenance builds on that foundation, alongside applications including Mesh, MailProxy, MCP Server, Marketplace and the AI provenance assistant in System Demo. These applications help us refine the security features, APIs and usability you can draw on in your own projects. You can adopt the capabilities you need without adopting the whole collection.
LockWire is in pre-release development. Features and APIs may change as we learn. Two sites explain the work in more detail:
- lockwire.org — product documentation, adoption guidance, release availability and measured compatibility results.
- lockwirelabs.com — the LockWire company site, including the product line and company information.
This site describes Veraccord Labs LLC, the parent entity.
How the source is organized
lockwirecontains the security framework and Saddle lifecycle tooling, along with framework applications and examples.lockwire-aicontains the AI provenance work built on the framework.lockwire-system-demobrings capabilities and applications together in a system demonstration that consumes the framework as an adopter does.
Development repositories are currently private. The LockWire GitHub organization is the home for public source as repositories open for release. Repository organization does not define a required adoption tier.
How LockWire is developed
Every change is developed under a security development lifecycle based on IEC 62443-4-1, and the framework is designed to provide the security controls the standard calls for. We publish a control catalogue: which controls we provide, and where each one lives in the code.
Each control names the IEC 62443-3-3 / -4-2 section that requires it. Because the standard applies different requirements at different Security Levels, the framework takes a target Security Level as a build input and selects the relevant requirements for you. The Security Level a finished product or system achieves depends on the whole design and how it is deployed, so treat the build input as a starting point.
LockWire is built to take part in a high-security product, up to and including one targeting SL-4, given careful system and product design.
The determination remains the integrator's and its assessment a third party's — but nothing in the framework is intended to be the constraint on how high that target can be.
Licensing and availability
Software license terms are specified in the applicable repository’s LICENSE files. Check lockwire.org for release announcements, download availability and evaluation guidance. Product descriptions explain the features we intend to release; availability and measured interoperability results are reported separately.
The company page on lockwirelabs.com carries the LockWire trademark information and publication channels.