# Introduction

**seekrit is a zero-knowledge secrets manager and credential broker for AI agents** — and for
teams and machines too. It stores your API keys, database URLs, and other secrets, and hands them
to your applications — in local development, Docker builds, CI, Kubernetes, and AI-agent sandboxes
— without the server ever seeing a plaintext value.

## How it works, in three lines

1. **You encrypt.** Secrets are encrypted in your browser or CLI, with a key that only ever exists
   on your side. The server receives ciphertext.
2. **seekrit stores and distributes.** The API — running on Cloudflare's global edge — keeps the
   ciphertext and hands each authorized person, machine, or agent a copy of the environment's key
   wrapped just for them.
3. **Your runtime decrypts.** The CLI, a service token, or an AI agent unwraps that key locally and
   injects the plaintext straight into your process — never back to the server.

The result: one place to manage every secret, injected with one command everywhere your code runs,
that the backend is cryptographically unable to read.

> **Note:** **Are you (or is your) AI agent building with seekrit?** seekrit has a hosted
>   [MCP server](/docs/mcp) an agent can self-register with and connect to in one request — no
>   human, no install. Start with the [MCP server page](/docs/mcp) or the deeper
>   [AI agents guide](/docs/guides/ai-agents). Send `Accept: text/markdown` to read the homepage,
>   docs, or blog at their usual URLs. [`/llms.txt`](/llms.txt) links to individual Markdown files,
>   and [`/llms-full.txt`](/llms-full.txt) collects the docs and articles in one file.

## Zero-knowledge by design

The defining property of seekrit is that **encryption keys are generated and used entirely on
the client**. When you add a secret in the web dashboard or CLI, it is encrypted in your browser
or on your machine before it is uploaded. The API — a Cloudflare Worker backed by managed
Postgres — only ever stores ciphertext. A full database dump reveals metadata (names, versions, timestamps) but no
secret values.

This is achieved with **envelope encryption**:

- Each **environment** has its own AES-256 data key (DEK).
- Secrets are encrypted with that DEK.
- The DEK is **wrapped** (encrypted) individually to each person or service token that should
  have access, using their public key.
- A user's private key is itself encrypted with a passphrase-derived key, so any device can
  fetch it and unlock it locally — the passphrase never leaves the client.

See [Encryption model](/docs/concepts/encryption) for the full picture.

## The pieces

seekrit has three parts:

- **Web dashboard** — create orgs, applications, and environments, and manage secrets with
  client-side encryption. Sign in with Google, GitHub, or an email and password (via Stytch).
- **CLI** (`seekrit`) — link a project directory to an environment and inject decrypted secrets
  into any command, or export them as `dotenv`/`json`/`shell`.
- **API** — a Hono Worker on Cloudflare with Postgres (via Hyperdrive) and KV, exposing an
  org-scoped REST API and an append-only audit trail.

## Built to scale, everywhere

Because the server only ever holds ciphertext, it can be cached anywhere without becoming a
liability. seekrit runs on Cloudflare's global edge, caches encrypted secrets close to your
workloads (keyed per caller, so tenants never share an entry), and serves the resolve hot path — every container, CI
job, and agent fetching its secrets on boot — from one org's laptop up to tens of thousands of reads
a day, with no infrastructure of your own. See [Scale & the edge](/docs/concepts/scale).

## Where to go next

### Getting started

- [MCP server (for AI agents)](/docs/mcp) — AI agents start here: what seekrit is and how to self-register and connect to the hosted MCP server in one request — no human, no install.
- [Quickstart](/docs/quickstart) — Sign in, encrypt your first secret, and inject it into a command.
- [Examples](/docs/examples) — A cookbook: composability, one secret set across every runtime, and agent workflows.

### Concepts

- [Encryption model](/docs/concepts/encryption) — Envelope encryption: data keys, key wrapping, passphrase keys.
- [Architecture](/docs/concepts/architecture) — Orgs, apps, environments, and the Cloudflare building blocks.
- [Scale & the edge](/docs/concepts/scale) — Why zero-knowledge distributes globally: edge-cached ciphertext at any scale.
- [Access & key grants](/docs/concepts/access-control) — Roles, per-principal key grants, revocation, and rotation.
- [Customer-controlled recovery](/docs/concepts/recovery) — Regain environment access with a quorum of custodians — no keys held by seekrit.
- [Managed keys (KMS)](/docs/concepts/kms) — Client-side managed keys for application-layer encryption and signing.
- [Security model](/docs/concepts/security) — What the server can and cannot see; the threat model.
- [Temporary access](/docs/concepts/temporary-access) — Short-lived credentials for databases, cloud services, networks, and AI tools.
- [Secret rotation](/docs/concepts/rotation) — Managed, scheduled replacement of stored credentials — and the boundary it needs.
- [Vault trust model](/docs/concepts/vault) — How your end users' credentials are held for an agent without you, your agent, or seekrit ever holding a plaintext.

### Managing secrets

- [Web dashboard](/docs/guides/web-app) — Sign in, set up keys, and manage secrets in the browser.
- [CLI](/docs/guides/cli) — Install, link a project, and inject secrets into any command.
- [Environments & groups](/docs/guides/environments) — Share secrets with groups; layer .env and process env on top.
- [Branch configs](/docs/guides/branches) — Throwaway per-PR and preview environments that inherit from a real one and delete themselves.
- [Secret references](/docs/guides/references) — Build one secret out of others: stored literally, expanded on read, so a rotation updates everything that references it.

### Agents & MCP

- [AI frameworks](/docs/guides/frameworks) — Start here for agents: LangGraph, Mastra, Pydantic AI, the AI SDK, CrewAI, LlamaIndex, LiteLLM, and the OpenAI Agents SDK or hosted Agents API.
- [AI agents](/docs/guides/ai-agents) — Drive seekrit from Claude Code and other MCP clients: the hosted metadata server plus the local crypto server.
- [Vault (end-user credentials)](/docs/guides/vault) — Let your users connect their accounts to your agent: a hosted consent page, custody seekrit cannot read, and an executor in your own Cloudflare account that applies the credential at the moment of use.
- [Credential broker](/docs/guides/agent-proxy) — Credential brokering for agents: the workload holds a placeholder, an egress proxy swaps in the real secret on the way out.
- [Agent sandboxes](/docs/guides/sandboxes) — Get secrets into E2B, Modal, Daytona, Vercel Sandbox, Cloudflare Sandbox, Cloudflare Computer, Fly.io Sprites, Boat and boxd — or keep them outside the sandbox entirely.

### Code & runtimes

- [Language SDKs](/docs/guides/sdks) — Resolve and decrypt secrets from your own code — Python, Go, JS/TS, and Ruby.
- [React & Next.js](/docs/guides/react) — Read secrets in a server component with one resolve per render, make handing one to the client a render-time error, and let the browser hold a placeholder instead of a key.
- [Replace dotenv (Node.js)](/docs/guides/dotenv) — Migrate a JavaScript/Node project off a plaintext .env file.
- [Vite plugin](/docs/guides/vite) — Resolve an environment straight into Vite — process.env for the build, and only the prefixed names in the bundle.
- [Jupyter notebooks](/docs/guides/notebooks) — One call at the top of a notebook loads an environment — without a pasted token or secret values in saved cell outputs.
- [seekrit-run launcher](/docs/guides/run) — Tiny static binary: inject secrets and exec, for CI and containers.
- [WebAssembly components](/docs/guides/wasm) — Give a WASM guest its secrets without giving it a token — a WASI component that resolves and decrypts inside the sandbox, on Spin, wasmCloud, or wasmtime.
- [Fermyon Spin](/docs/guides/spin) — Declare the seekrit component as a Spin dependency: the token lives in a Spin variable, and no component in the app holds a credential.

### Deploy & CI

- [Cloudflare Python Workers](/docs/guides/cloudflare-python-workers) — Resolve and decrypt inside a Python Worker with one token binding and native async fetch.
- [CI/CD & containers](/docs/guides/ci-cd) — Wire seekrit into pipelines and image builds.
- [Neon Functions](/docs/guides/neon-functions) — Resolve third-party credentials inside a Neon Function while Neon supplies branch-specific database access.
- [Kubernetes (ESO)](/docs/guides/kubernetes) — Sync secrets into Kubernetes with the External Secrets Operator.
- [HashiCorp Nomad](/docs/guides/nomad) — A Nomad secret provider plugin: jobs name credentials, and the client node decrypts them.
- [wasmCloud](/docs/guides/wasmcloud) — Run seekrit as a wasmCloud secrets backend: components ask wasmCloud for secrets, and your own lattice decrypts them.
- [SF Compute (GPU nodes)](/docs/guides/sf-compute) — Bootstrap rented H100 nodes with one token instead of a startup script full of keys.
- [Terraform provider](/docs/guides/terraform) — Manage applications, environments, tokens, grants, and secrets as code — with no secret value in Terraform state.
- [Third-party sync](/docs/guides/third-party-sync) — Push secrets to platforms whose runtime you don't control — Vercel, Cloudflare, AWS, and a dozen more.
- [Self-hosted provisioner](/docs/guides/provisioner) — Run the remote executor so seekrit never sees your database admin credential.

### Access & security

- [Service tokens](/docs/guides/service-tokens) — Machine credentials for CI, Docker, Kubernetes, and agents.
- [Workload identity federation](/docs/guides/workload-identity) — seekrit as an OIDC identity provider: workloads reach AWS, Google Cloud, OpenAI and Anthropic with short-lived tokens instead of stored keys.
- [Approval workflows](/docs/guides/approvals) — Require review before a secret in a protected environment changes — without a reviewer ever seeing the value.
- [Honey tokens](/docs/guides/honey-tokens) — Decoy credentials that unlock nothing and alert you the moment anyone tries to use them.
- [Rotate secrets on a schedule](/docs/guides/rotation) — Replace a stored credential on a schedule, re-keying the database account with it.
- [Set up recovery](/docs/guides/recovery) — Configure and exercise customer-controlled M-of-N recovery from the CLI and dashboard.
- [Export & break-glass recovery](/docs/guides/export) — Take everything out as one signed file, and open it offline — with a passphrase, a token, or a custodian quorum.
- [Managed keys (KMS)](/docs/guides/kms) — Create managed keys and use them to encrypt, decrypt, and sign.
- [AWS KMS drop-in](/docs/guides/kms-aws) — Point any AWS SDK at seekrit-kms: KMS-compatible envelope encryption, zero-knowledge.

### Operations

- [Audit log export](/docs/guides/audit-export) — Stream your audit trail to an OTLP endpoint for SIEM and observability.
- [Telemetry (OpenTelemetry)](/docs/guides/telemetry) — Export traces, metrics, and logs from the seekrit services you run yourself to your own OTLP collector.
- [Email notifications](/docs/guides/notifications) — Which transactional emails seekrit sends, and how to manage them.
- [Plans & billing](/docs/guides/billing) — See your plan and usage, upgrade, and manage payment from the dashboard.

### Reference

- [CLI commands](/docs/reference/cli) — Every command, flag, and environment variable.
- [REST API](/docs/reference/api) — Endpoints, auth, and payloads exposed by the API worker.

### Self-hosting

- [Deploy on your infrastructure](/docs/self-hosting) — Run seekrit in your own Cloudflare account and Postgres database for compliance, residency, or isolation.
