The code examples in your docs should run
DocsAlive extracts the fenced examples in a documentation repository, runs or checks the ones it supports in an isolated sandbox, and separates likely docs bugs from noise. Optionally, it can draft a small fix for a person to review. Nothing merges without a maintainer.
Send a public GitHub or GitLab repository you own or maintain. The team runs the engine on up to 40 docs pages and emails the real report within 2 business days. Free, no signup.
From a docs repo to a classified report
Detection, execution and triage are deterministic. A model is involved only if your organization configures a provider for optional fix drafting.
Extract every fence
It detects MkDocs, Mintlify, Docusaurus or a ReadMe export from the repository’s config, or falls back to plain Markdown and MDX. Each fenced block is recorded with its page and line number. One variant is selected from each recognized tab group.
Run in a fresh sandbox
Supported blocks run in page order in a new container per page: unprivileged user, read-only root filesystem, Linux capabilities dropped, with memory, CPU, process and time limits. Each page starts clean, so later snippets on the same page can still see earlier variables.
Triage the actual error
Results are classified by matching the error, not the exit code alone. Categories such as api-drift, invalid-syntax, stale-output and package-not-found can count as likely docs bugs. Missing context, credentials and network failures are kept out of that count.
What it runs, and what it does not
DocsAlive executes Python (including >>> sessions), JavaScript on Node 20, simple TypeScript after stripping basic annotations, shell, and curl or raw HTTP blocks. JSON and TOML are validated. OpenAPI files are parsed and $refs are resolved; that is a structural check, not a request to your API.
Go, Rust, Java, Ruby, PHP, C#, Kotlin and Swift are recognized but not executed. Full TypeScript and JSX or TSX are not judged. Examples that need API keys are classified as needing credentials, not run with real keys. VitePress is not a detected framework: those projects are read as plain Markdown, and VitePress code groups are not treated as alternatives.
The engine can still raise false alarms, for example a “before” snippet in a migration guide that shows an old API on purpose. The results page publishes real runs on three open-source docs sites, including cases where the engine was wrong.
Try it on a public repo
The Health Check is run by the team and emailed back. It is not instant, and there is no self-serve CLI download. The CLI and GitHub App are set up during onboarding after you subscribe or apply for the Open source plan.
If a model provider is configured, DocsAlive can draft the smallest fix, re-run the page and keep the fix only if it passes. Fix pull requests open as drafts. A person still decides.
- Open source
- $0 per month, public OSI-licensed projects
- Team
- $299 per month
- Growth
- $699 per month
- Scale
- from $1,499 per month
Paid plans are billed monthly in USD and onboarded individually after you subscribe. See pricing for current terms.
See which of your examples still work.
Send a public repository you own or maintain. The team runs the same engine used on paid plans and emails the report within 2 business days.