Get started

LockWire's front door is the Easy Button: one dependency and one line that give a Rust application HTTPS with a real certificate chain — trusted on localhost and your LAN, auto-renewed, and revocation-checked on every use. No browser warnings, and no openssl incantations.

let server = lockwire::serve(app)
    .https_easy_button() // trusted local CA, auto-renewal, revocation checked
    .await?;

The same pattern extends across the suite: passkey and OIDC login, signed updates, tamper-evident audit, and authenticated time each have a one-line secure default, with fail-loud guards that turn an insecure configuration into a build-time error rather than a production incident.

Where things stand

LockWire is in pre-release development, and this page grows into the full five-minute walkthrough — with CI-verified snippets — as the crates publish. The repositories go public as each tier reaches release; their canonical homes are github.com/lockwire-org/lockwire (the umbrella crate and CLI, whose getting-started guide this page will point at), lockwire-sec, lockwire-ai, and lockwire-ssdl. The crate names are already reserved on crates.io.