docs.dev vs Ship Stacks

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

Full-stack templates that ship on day one. Auth, OAuth, Stripe, S3, email, AI chat, and Docker, already wired across 17 production-ready backends in 10 languages. Pick a...

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 Ship Stacks

Full-stack templates that ship on day one. Auth, OAuth, Stripe, S3, email, AI chat, and Docker, already wired across 17 production-ready backends in 10 languages. Pick a language, configure at checkout, ship. The crash-and-restart pattern was designed once, then hand-ported into each language's own concurrency model, five of them run real production apps today. The most-run base in the family, several products built from this one starting point. Server-rendered islands hydrate in place, no separate SPA build, no client router.