CI/Lock vs docs.dev

CI/lock collects trusted telemetry across every checkpoint between commit and production, CI/CD builds, security scans (SAST/DAST/SBOM), runtime + cluster integrity...

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

About CI/Lock

CI/lock collects trusted telemetry across every checkpoint between commit and production, CI/CD builds, security scans (SAST/DAST/SBOM), runtime + cluster integrity (Falco, Linkerd mTLS, kube-bench), and continuous compliance (CSPM, FIPS, STIG). Signed as in-toto evidence for FedRAMP 20x, the EU Cyber Resilience Act, NIST 800-204D, SLSA, CMMC, and human-controlled cryptographic gates for AI-agent workflows. Witness-compatible, built on the rookery attestor factory. The DSSE + in-toto envelopes CI/lock emits are the same shape across every stage.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.