Getting started
What you need, how Keyward Desktop will be installed and activated, how a first caller is allowed and a first secret kept, and where to go next; written against the design, and marked where nothing can be done yet.
Documentation
How Keyward works
Written for the person doing the work: what each thing does, what it does not do, and where the edges are.
Start
Verify a download
How to check that an installer is the one that was released, before you run it.
Licenses and seats
What a license key is, what a seat is, how a computer is activated, and what happens when a license ends. One license covers Keyward Desktop and the command line, and one seat covers both on a computer.
Updates
How each program finds a new release of itself, how it decides to trust it, and what it does when you agree to install it.
Products
What Keyward is
Three parts, one product. The server you run, the vault on your own Windows computer, and the one door every AI session and developer tool uses; what each does, why they are separate, and what stays where.
Keyward Server
The secrets, credentials, certificates and machine-identity platform at the centre of Keyward, what it is a fork of, how its provenance travels with every build, and what its first build is and is not.
Keyward Desktop and the Keyward Service
The vault on your own Windows computer, as it is designed; the service that holds it, the key the TPM keeps, how a program is identified when it asks, what you approve, and what is imported from Credential Manager.
AI sessions
How Claude Code, Codex, Claude Desktop, claude.ai and ChatGPT use Keyward, as designed; one MCP server with a local and a remote transport, and the rule that a model gets a handle, not a value.
Credential helpers
How git, Docker, Python's keyring and any command get their secrets from Keyward instead of from files and environment variables, as designed, and the one rule every helper keeps.
Enterprise
What Keyward Enterprise means, as designed; enrolment of computers with a Keyward server, mirrored projects, central audit and policy, the connector and the relay; and what the words do not mean.
Status
What exists, what each part does today, what is proven and what is not, and what comes next, said plainly and kept current.
Security
Signing in
How people at Exprezoe sign in to Keyward Desktop and the command line with Exprezoe Identity in place of a license key, what the programs keep afterwards, and how to sign out.
Reference
Troubleshooting
What the programs and this site say when something does not work, what it means, and what to do.
The update and license API
The endpoints Keyward Desktop and the command line themselves talk to, for people who run a mirror, automate a deployment or want to know exactly what is sent.