docs: add ZeroKMS vs HSM comparison + merge Cloud KMS into AWS KMS#31
Open
coderdan wants to merge 4 commits into
Open
docs: add ZeroKMS vs HSM comparison + merge Cloud KMS into AWS KMS#31coderdan wants to merge 4 commits into
coderdan wants to merge 4 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
6 tasks
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.
1f51532 to
a398e05
Compare
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.
8b9e917 to
5b1791e
Compare
Showcase the new ZeroKMS vs HSM page on the comparisons landing page, and refresh the AWS KMS card to reflect its added architecture content.
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrates the comparison docs from cipherstash-js-suite PR #364 into this Fumadocs repo.
Changes
comparisons/zerokms-vs-hsm.mdx— ZeroKMS vs Hardware Security Modules (WIP, retains the original 5TODOs) +public/images/hsm.pngcomparisons/aws-kms.mdxrather than shipped as a separate page (the two overlapped heavily).aws-kms.mdxnow has: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/docs/...scheme to/stack/...Verification
bun run buildpasses — 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.