Skip to content

docs: add ZeroKMS vs HSM comparison + merge Cloud KMS into AWS KMS#31

Open
coderdan wants to merge 4 commits into
mainfrom
docs/zerokms-comparisons
Open

docs: add ZeroKMS vs HSM comparison + merge Cloud KMS into AWS KMS#31
coderdan wants to merge 4 commits into
mainfrom
docs/zerokms-comparisons

Conversation

@coderdan

@coderdan coderdan commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Migrates the comparison docs from cipherstash-js-suite PR #364 into this Fumadocs repo.

Changes

  • New: comparisons/zerokms-vs-hsm.mdx — ZeroKMS vs Hardware Security Modules (WIP, retains the original 5 TODOs) + public/images/hsm.png
  • Merged, not added: the migrated ZeroKMS vs Cloud KMS content was folded into the existing comparisons/aws-kms.mdx rather than shipped as a separate page (the two overlapped heavily). aws-kms.mdx now has:
    • a new Architecture & trust model section (zero-knowledge, per-record keys, blast radius, 14× perf, audit, deployment), noting GCP/Azure share the same architecture
    • the existing Developer experience comparison (all code examples retained)
    • the comparison table split into Architecture and Developer experience, plus a Migration path
  • Both pages added to the comparisons overview (index.mdx) and nav (meta.json)

Conversion notes (Markdoc → Fumadocs MDX)

  • {% callout %} / {% callout-block %}<Callout>; {% figure %} → MDX image
  • {% d2 %} placeholders → {/* TODO */} comments (no D2 renderer here); original source preserved inline
  • Internal links remapped from the source /docs/... scheme to /stack/...

Verification

bun run build passes — link validation clean, all static pages generated.

Follow-ups

Remaining work (the 5 vs-hsm TODOs and the diagram placeholder) is tracked in #32.

Depends on #33 (EQL generator fix), already merged. Original PR #364 can be closed once this lands.

@vercel

vercel Bot commented Jun 23, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
public-docs Ready Ready Preview, Comment Jun 23, 2026 9:34am

Request Review

Migrated from cipherstash-js-suite PR #364 (Markdoc apps/docs) into the
Fumadocs content tree. Callouts/figure converted to MDX; placeholder D2
diagrams preserved as TODO comments. vs-hsm retains its WIP TODOs.
The standalone zerokms-vs-cloud-kms page overlapped heavily with the
existing aws-kms page. Fold its architecture/trust-model content into
aws-kms.mdx (kept as the canonical, SEO-established URL) as a new
'Architecture & trust model' section, alongside the existing
developer-experience comparison. Split the comparison table into
Architecture and Developer experience, and add a migration path.
Remove the standalone page and its nav entry.
@coderdan coderdan force-pushed the docs/zerokms-comparisons branch from 8b9e917 to 5b1791e Compare June 23, 2026 09:05
Showcase the new ZeroKMS vs HSM page on the comparisons landing page,
and refresh the AWS KMS card to reflect its added architecture content.
@coderdan coderdan changed the title docs: add ZeroKMS vs Cloud KMS and vs HSM comparisons docs: add ZeroKMS vs HSM comparison + merge Cloud KMS into AWS KMS Jun 23, 2026
Optimize for machine readers extracting facts, modeled on the fhe.mdx
page in this repo:
- add an entity-taxonomy table (AWS KMS / ZeroKMS / SDK / Proxy) so the
  distinct products aren't conflated
- replace persuasion with neutral, extractable claims; cut redundant
  encrypt/decrypt repetition (one canonical example + tables)
- source the sub-5ms latency claim (Artillery benchmark); flag the
  unsourced 14x throughput figure with a TODO until a public benchmark
  is cited; standardize on 14x (was inconsistently 14x/100x elsewhere)
- add explicit limits (PostgreSQL-oriented search, OIDC dependency,
  application-layer scope) for a balanced comparison
- tighten 'zero-knowledge' vs 'distributed trust' terminology
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant