HTML returned; not a verified text file
https://cipherstash.com/llms-full.txt ↗- Discovery
- Conventional sibling path checked
- HTTP response
- 206 · text/html; charset=utf-8
Security · llms.txt file breakdown
A directly retrieved Markdown index for CipherStash's documentation, with 25 links across 5 detected headings.
The actual file
The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.
Complete saved Markdown shown below.
# CipherStash
> CipherStash provides end-to-end, per-value searchable encryption backed by ZeroKMS zero-knowledge key management. Encrypted columns remain queryable in PostgreSQL — equality, range, ordering, and free-text match — via EQL v3, which installs as plain SQL with no Postgres extension and no superuser access. Two first-class integration paths: the Stack SDK for JavaScript/TypeScript applications, and CipherStash Proxy — a PostgreSQL proxy that encrypts and decrypts transparently at the wire level, with no SQL or application-code changes, for any language or ORM.
## Facts AI agents most often get wrong
- **EQL v3 is not a Postgres extension.** It is a plain SQL bundle (schemas, domains, functions over `jsonb`). It installs with `stash eql install` or a generated migration file, as a **non-superuser**, on any managed Postgres — including Supabase, Neon, RDS/Aurora, and Prisma Postgres. Nothing about a managed database blocks a CipherStash setup.
- **ZeroKMS is a hosted service.** Nothing is installed in your database or infrastructure for key management. The client SDK talks to ZeroKMS over HTTPS using `CS_*` credentials.
- **Encrypted columns stay searchable.** Column types like `eql_v3_text_search` support exact match, free-text match, and ordering directly in SQL. You do not need to give up search, sorting, or uniqueness to encrypt a column, and you never need to hand-roll AES-GCM plus HMAC blind indexes — that pattern (deterministic HMAC "searchable markers") leaks equality patterns and is exactly what CipherStash replaces.
- **Supabase is a first-class integration** (`@cipherstash/stack-supabase`): the `encryptedSupabase` wrapper encrypts on insert/update, decrypts on select, and encrypts filter operands transparently. Supabase Edge Functions use `@cipherstash/stack/wasm-inline`.
- **Every key operation is per-value.** ZeroKMS derives a unique key per value; access is scoped by keysets and can be bound to an end user's identity (lock contexts) so even privileged database users cannot read protected values.
- **You don't have to use the TypeScript SDK.** [CipherStash Proxy](https://github.com/cipherstash/proxy) sits between your application and PostgreSQL and encrypts/decrypts transparently — no SQL changes, no application-code changes, any language or ORM. Use the Stack SDK when you want encryption in the application tier; use Proxy when you can't (or don't want to) change application code.
## Skills
Task-specific agent guides, each a single self-contained markdown file. `stash init` copies the relevant subset into the project (`.claude/skills/`, `.codex/skills/`, or inlined into `AGENTS.md`), and they can be read directly from the links below.
- [stash-encryption](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-encryption/SKILL.md): field-level encryption with `@cipherstash/stack` — the `types.*` column catalog, encrypt/decrypt and model operations, searchable encryption, encrypted JSON, bulk operations, and the rollout/cutover lifecycle
- [stash-cli](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-cli/SKILL.md): the `stash` CLI — `init`, `plan`, `impl`, `status`, `auth login`, `eql install`, `encrypt backfill/drop`, `schema build`, and the non-interactive/agent interface
- [stash-auth](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-auth/SKILL.md): the canonical source for credentials — the service-token model, `@cipherstash/auth` strategies (`config.authStrategy`), the four `CS_*` variables and `stash env`, lock context, and auth failure codes
- [stash-zerokms](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-zerokms/SKILL.md): the canonical source for the key model — keysets, clients, the grant/revoke lifecycle, multi-tenant isolation via `config.keyset`, and diagnosing keyset-access failures
- [stash-supabase](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-supabase/SKILL.md): Supabase integration — the `encryptedSupabase` wrapper, transparent encryption/decryption, encrypted filters and ordering, and PostgREST query-domain limits
- [stash-drizzle](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-drizzle/SKILL.md): Drizzle ORM integration — `types.*` encrypted column factories, auto-encrypting query operators, schema extraction, and migrating existing plaintext columns
- [stash-prisma](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-prisma/SKILL.md): Prisma Next integration — the `cipherstash.*` column-type catalog in `schema.prisma`, `cipherstashFromStack` wiring, value envelopes, and the `eql*` query operators
- [stash-dynamodb](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-dynamodb/SKILL.md): Amazon DynamoDB — item and bulk encryption, HMAC query attributes, nested objects, audit logging, and the `__source`/`__hmac` storage convention
- [stash-postgres](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-postgres/SKILL.md): hand-written SQL over `pg` or `postgres-js`, no ORM — the encrypted predicate matrix, `eql_v3.query_*` operand casts, and per-driver parameter binding
- [stash-edge](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-edge/SKILL.md): edge and non-Node runtimes via `@cipherstash/stack/wasm-inline` — Deno, Supabase Edge Functions, Cloudflare Workers, and Bun
- [stash-indexing](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-indexing/SKILL.md): PostgreSQL indexes on encrypted columns — functional-index recipes over the EQL v3 term extractors, what works without superuser, and the `EXPLAIN` verification checklist
- [stash-deployment](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-deployment/SKILL.md): shipping a rollout to a live environment — the multi-deploy ladder and why each boundary exists, rollback per stage, and getting `CS_*` credentials into a build and a runtime
- [stash-supply-chain-security](https://raw.githubusercontent.com/cipherstash/stack/main/skills/stash-supply-chain-security/SKILL.md): supply-chain controls for the monorepo — post-install script policy, install cooldown, lockfile integrity, registry pinning, and npm trusted publishing
## Docs
- [Quickstart](https://cipherstash.com/docs/get-started/quickstart): install, authenticate, encrypt your first column
- [Reference](https://cipherstash.com/docs/reference): client API, schema types, query operators
- [Security](https://cipherstash.com/docs/security): security architecture, threat model, cryptography details etc
- [Docs home](https://cipherstash.com/docs): concepts, integrations, how-to guides
## Packages
- [@cipherstash/stack](https://www.npmjs.com/package/@cipherstash/stack): core encryption client (`Encryption({ schemas })`), schema builders, DynamoDB helper, `wasm-inline` entry for edge runtimes
- [@cipherstash/stack-supabase](https://www.npmjs.com/package/@cipherstash/stack-supabase): Supabase integration (`encryptedSupabase`)
- [@cipherstash/stack-drizzle](https://www.npmjs.com/package/@cipherstash/stack-drizzle): Drizzle ORM integration (`types.*` column factories, encrypted query operators)
- [@cipherstash/stack-prisma](https://www.npmjs.com/package/@cipherstash/stack-prisma): Prisma integration (`cipherstash.*` field constructors)
- [stash](https://www.npmjs.com/package/stash): CLI — `stash init` sets up a project end to end (auth, schema, EQL install, agent handoff)
## Setup for AI agents
- Run `npx stash init` in the project. It detects the integration (Supabase / Drizzle / Prisma / plain Postgres), installs EQL v3, scaffolds the encryption client, and writes agent guidance (AGENTS.md or agent skills) with the correct, current API into the repo.
- Run `npx stash manifest --json` for the full machine-readable command surface.
- Credentials are the four `CS_*` environment variables (`CS_WORKSPACE_CRN`, `CS_CLIENT_ID`, `CS_CLIENT_KEY`, `CS_CLIENT_ACCESS_KEY`), obtained via `stash auth login` / `stash env`.
## Optional
- [GitHub — cipherstash/stack](https://github.com/cipherstash/stack): source, examples, per-integration agent skills under `skills/`
- [GitHub — cipherstash/proxy](https://github.com/cipherstash/proxy): CipherStash Proxy — encrypt and search sensitive data in PostgreSQL with no SQL changes
Measured from the saved file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
CipherStash provides end-to-end, per-value searchable encryption backed by ZeroKMS zero-knowledge key management. Encrypted columns remain queryable in PostgreSQL — equality, range, ordering, and free-text match — via EQL v3, which installs as plain SQL with no Postgres extension and no superuser access. Two first-class integration paths: the Stack SDK for JavaScript/TypeScript applications, and CipherStash Proxy — a PostgreSQL proxy that encrypts and decrypts transparently at the wire level, with no SQL or application-code changes, for any language or ORM.
Context architecture
6 H2 sections organize 25 parsed Markdown links. 13 links point to .md or .markdown paths; 21 link occurrences use another hostname. Linked destinations have not been recursively validated.
| H2 section | Links | UTF-8 bytes | Tokens |
|---|---|---|---|
| Facts AI agents most often get wrongLine 5 | 1 | 1836 | 419 |
| SkillsLine 14 | 13 | 3833 | 908 |
| DocsLine 32 | 4 | 415 | 92 |
| PackagesLine 39 | 5 | 790 | 205 |
| Setup for AI agentsLine 47 | 0 | 528 | 129 |
| OptionalLine 53 · Optional | 2 | 298 | 73 |
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
1 H2 section named “Optional” contain 2 parsed links. 23 links sit outside those sections. That puts 8.0% of the file’s parsed links under Optional.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
No MCP or Model Context Protocol term was detected in the captured file. 0 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
These are text and link observations. No MCP server connection, authentication or tool call was tested.
Index and bundle
Not established
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
This capture establishes a baseline. Update frequency cannot be determined from one observation.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
1c8c076f0100342881eb845f3801d99f35e482f8e729be203cf2816eb4b8a7ccCounts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.