docs.dev vs Hiver

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...

Fast, replayable sandboxes for every browser, file, network, and tool action.

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.

About Hiver

Fast, replayable sandboxes for every browser, file, network, and tool action. Give agents a real working environment with governed files, policy-gated actions, and full replay across every run. Give agents access to files from a variety of file systems with precise ACLs: read-only, write-only, scoped by user, team, org, or workflow. Gate network access, protect credentials, and enforce policy around every file, API, tool, and action an agent uses. Replay every browser action, file change, network request, tool call, and approval across the full agent run.