Your code runs in a box we throw away.
DocsAlive executes code from your documentation, so isolation and data handling are the core of the product, not an add-on. Below is exactly what we do, in plain language, and what we don't have yet.
At a glance
Sandboxed
Each docs page runs in its own fresh, unprivileged, locked-down container.
No code retention
Repository checkouts are deleted when the run ends.
Least privilege
Only the GitHub permissions needed to read, report and propose.
Human approval
Changes are proposed as draft PRs on our own branches. Your team reviews and merges.
Execution sandbox
Code from your docs runs only inside isolated containers, not directly on our hosts. For every page, the runner starts a new container from a minimal image and destroys it when the page finishes. Your repository itself is not mounted. The container only receives the extracted snippets and our test driver, both read-only.
| Control | Setting |
|---|---|
| User | Unprivileged (uid 10001), never root |
| Linux capabilities | All dropped (--cap-drop ALL) |
| Privilege escalation | Blocked (no-new-privileges) |
| Filesystem | Read-only root. Writable scratch space is in-memory and discarded |
| Resources | 1 CPU, 1 GB memory, 256 processes per container by default |
| Time | Per-step timeout (60 s default) and a hard per-page kill |
| Lifetime | One container per page, removed on exit (--rm) |
| Network | On by default so documented installs and API calls work. Can be disabled per project |
| Kernel isolation | gVisor (runsc) supported for an additional kernel boundary |
Data handling & retention
What we access
A shallow clone of each repository you connect, or of the public repository you enter in the Health Check, so we can read its docs. Only the code blocks extracted from your docs are executed. Nothing else in the repository runs.
What we keep
- Source code: not retained. Clones are shallow, written to a temporary directory and deleted as soon as the run ends, whether it succeeds or fails.
- Reports: per-block results: file path, line number, language, category, a one-line reason and an error excerpt capped at 700 characters. Health Check reports are deleted after 90 days.
- Account data: the minimum needed to run your account and bill you. See the Privacy Policy.
What we never do
- Sell or share your code or reports.
- Train models on your code or docs.
- Write to any branch other than our own
docsalive/fix-*branches.
AI model providers
Detection, execution and triage are deterministic and use no AI. A language model is only involved when fix drafting is turned on. Then we send the affected docs page (capped at 16,000 characters), the failing snippet and its error output to the provider your organization approves. Your application source code is not sent. You can run DocsAlive with fix drafting turned off, and every other feature still works.
GitHub permissions
The GitHub App requests only what it needs, and you choose which repositories it can see.
| Permission | Access | Why |
|---|---|---|
| Metadata | Read | Required by GitHub for every app |
| Contents | Write | Read docs, and push fix commits to docsalive/fix-* branches only |
| Pull requests | Write | Open fix PRs as drafts |
| Checks | Write | Post results and line annotations |
| Commit statuses | Write | Show the docs status on commits |
Webhooks are verified with an HMAC signature before we act on them.
A human approves every change
DocsAlive is designed not to merge anything. Fixes open as draft pull requests that show the original error and the passing re-run. Checks stay neutral when failures aren't docs bugs, so we don't block your merges on noise.
This website
No cookies, analytics, tracking pixels or third-party scripts. Fonts and assets are served from our own domain. See the Cookie notice.
Compliance status
We are an early-stage company and we'd rather be precise than impressive. No security measure is perfect, and the controls above reduce risk without eliminating it. We do not hold SOC 2, ISO 27001 or any other certification today. We'll update this page when that changes. A Data Processing Addendum is available to customers, and we're happy to answer security questionnaires.
Reporting a vulnerability
Email security@docsalive.com. We aim to acknowledge reports within 3 business days and to keep you updated. We don't intend to pursue legal action against good-faith research that follows our Acceptable Use Policy. Timeframes on this page are operational targets, not contractual commitments.