mirror of
https://github.com/hanzoai/site.git
synced 2026-11-20 21:21:13 +00:00
1 line
3.7 KiB
JSON
1 line
3.7 KiB
JSON
{"text":["kms.hanzo.ai","Hanzo KMS","Secrets management","Open KMS","Documentation","KMS","— Hanzo","IAM","Authz","Secrets","Audit","Zero Trust","gateway","Ready","payments-api","checkout-web","Building","docs-site","The service the session above is changing.","api.hanzo.ai","/v1/kms","Open in the console","Example project. Every name in it is one you would give your own.","Paste and ship","Paste this into any agent. It reads the skill manifest and calls KMS from there.","Agent prompt","api","Copy","Read https://hanzo.ai/skill.md and use Hanzo KMS in my project. Start with: hanzo kms secrets create","What it holds and how it holds it","A secret is a value under a path, a name and an environment, inside one organization. That is the whole model.","01","Sealed before it leaves you","Argon2id turns a passphrase into a key, HKDF-SHA256 turns that into the organization's key, and AES-256-GCM seals the value. The organization key stays on the client. Sharing with a colleague wraps that same key to their public key using a hybrid post-quantum exchange, so nobody has to send anybody a secret to share one.","02","Into the process, not into a file","Run a command with the secrets already in its environment, export a dotenv when a tool insists on one, or let the Kubernetes operator keep a Secret in step with what KMS holds. The CLI also reads your repository and its git history looking for values that escaped.","03","Replacing one is deliberate","Rotate is a command, and a write states the version it means to replace — so a second writer who read the old value is refused rather than quietly winning. Signing keys generate, sign and rotate through the same API, backed by threshold MPC.","04","Who read it, when, and why","Reads and writes land in an append-only record written by a single writer off the request path, so keeping it never slows a fetch. An AI agent's read is attributed to that agent by name, not to whichever human's key it borrowed.","05","One key, several languages","A CLI for a laptop and for CI. SDKs in Go, Node and Python over the same routes. In-cluster callers can take the binary ZAP transport instead of HTTP, and it enforces the identical token and role checks.","06","Fail closed, or do not start","Every call carries a Hanzo IAM token verified against a cached JWKS; HMAC and alg none are refused outright. The organization comes from the verified token, never from a field the caller sets. Outside development the daemon will not boot without an issuer, an audience and a JWKS URL — there is no accidental open mode. A secret can be marked so that any agent read waits for a person to approve it, or is refused.","AES-256","Sealed on your machine","K8s","Secrets kept in step","Every read recorded","MIT","Run it yourself","Nothing lands on disk","terminal","# Sign in, then point this directory at a path","kms","login","init","# Start the process with its secrets already in the environment","run","--","npm","start","# ...or write a dotenv, for a tool that insists on one","export","--format=dotenv","# Replace a value","rotate","DATABASE_PASSWORD","# Find the ones that already escaped, here and in git history","scan","Take them out of the repo","Use it hosted, or run the same binary yourself. The source is MIT and the client is where the encryption happens either way.","View on GitHub","Related capabilities","OIDC identity & orgs","Fine-grained access","Store once, sync everywhere","Get KMS","Secrets + key management","Apache-2.0","License:","hanzoai/kms","3 stars","Deploy to Cloud"],"links":["https://kms.hanzo.ai","https://docs.hanzo.ai/docs/openapi/kms/","/iam","/authz","/kms","/cloud/secrets","/cloud/audit","/cloud/zero-trust","https://hanzo.team/","https://github.com/hanzoai/kms","https://platform.hanzo.ai/deploy"]} |