Security at DocuSOR
DocuSOR is built around a simple principle: your code stays yours. Our cloud platform fetches what it needs, when it needs it, runs your verifications in isolated environments, and keeps none of your source code. Below is how our architecture, execution model, and infrastructure reflect that.
We don't store your source code.
DocuSOR does not store your source code. Repository content is fetched through the GitHub App or your GitLab connection for each run under scoped permissions and processed in transit. DocuSOR keeps the verified context for your repository and your run history, including each check's result and the output it produced. When you test one of your own docs, that Markdown file appears in its results. The MCP server serves the verified context DocuSOR keeps, never a copy of your code. Access is granted through the GitHub App or a GitLab token and can be revoked at any time by uninstalling the App or revoking the token.
We run your verifications without storing your code.
Each run executes your repository at a specific commit plus the checks stored in DocuSOR for it. Runs execute on DocuSOR's managed infrastructure in ephemeral, isolated containers. Repository content is fetched for each run and processed in transit. Your source code is never hosted or stored on our systems. The run container is destroyed when the run completes, whether it passes or fails; what is retained is the verified context and your run history. Checks can only be added by people and agents holding your organization's keys. When a docker-compose file is present, DocuSOR provisions services before the run and tears them down afterward (down -v), leaving no residual state.
Self-hosting (Enterprise)
Enterprise customers can run DocuSOR in their own infrastructure: the web app, backend API, and validation runner deploy on your hosts with your PostgreSQL database, and engineers sign in with your SSO (SAML or OIDC). Code, context, and run history stay on your network. An air-gapped option runs the credit License Manager on your side as well. Private runners are available as an add-on.
Compliance
SOC 2 Type I: compliant.
DocuSOR is SOC 2 Type I compliant as of July 23, 2026. We manage our controls program continuously through Vanta. For more information, please reference our Trust Center page at security.docusor.ai.
Infrastructure security
DocuSOR's production infrastructure is protected by a default-deny cloud firewall permitting only required inbound traffic. We run CrowdSec for intrusion detection and traffic filtering. Administrative access uses key-based SSH authentication (ed25519); password authentication is disabled. Public traffic is served through Cloudflare's edge network.
Data protection
Data is encrypted in transit using TLS. Our PostgreSQL datastore runs in an isolated container on private networking and is not exposed to the public internet. Customer data is always encrypted at rest.
Application security
DocuSOR is built and shipped through a GitHub-based development workflow. Container images are published to and pulled from a private registry. We monitor our dependencies for known vulnerabilities with GitHub Dependabot alerts and npm audit, and scan our container images with Trivy.
Vulnerability disclosure
Report a vulnerability.
If you believe you've found a security issue in DocuSOR, please email [email protected]. We'll acknowledge your report and work with you to resolve it. We ask that you give us a reasonable opportunity to address the issue before public disclosure.
