docs.dev vs Substructure

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

subs is an agent harness for the cloud. It runs an unprivileged agent loop with no system access. It uses MCP servers for tools. It can run locally or as a client and server.

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 Substructure

subs is an agent harness for the cloud. It runs an unprivileged agent loop with no system access. It uses MCP servers for tools. It can run locally or as a client and server. Create the project from the file, then give it your LLM key. Configure the engine to send a webhook to your system and take complete control over the agent loop and Slack agent behavior. You handle a webhook, customizing just the steps you care about.