Scoped GitHub connection
Moxie uses GitHub App installs so teams can choose exactly which repositories are available to a workspace.
// Security
Built for private repositories and reviewable automation.
Moxie Docs connects to GitHub, reads code, generates documentation, exposes MCP-ready context, and opens docs-only PRs when automation is enabled. The security model keeps repository access scoped, secrets server-side, and review decisions in your GitHub workflow.
Server-side credentials
Access tokens and secrets are stored server-side and are never exposed in the browser or shipped to client devices.
Workspace authorization
Workspace roles control who can reach repository docs, MCP context, settings, billing, and admin tools.
Secret-aware indexing
The indexer skips common secret files, generated assets, dependency folders, binary files, and paths excluded by repository rules.
Human-controlled automation
Friday Cleanup PRs are docs-only, source-cited, never auto-merged, and reviewed through your normal GitHub process.
Operational monitoring
Webhook processing, indexing jobs, auth events, billing events, and background automation record operational events for debugging and audit trails.
// Data handling
Clear handling for code, generated docs, and AI context.
Repository data
Moxie processes source files, manifests, docs, tests, and pull request events to generate docs, search results, recaps, and missing-doc alerts.
AI context
AI requests are assembled server-side from focused code and documentation chunks instead of sending an entire repository by default.
Retention and deletion
Workspace settings let admins pause automation, remove repository data, and delete an account. Support can help with exports or edge cases.
// Contact
Evaluating Moxie Docs for a private or enterprise repo?
Email contact@moxiedocs.com for security questions, data processing needs, deployment plans, or a guided first-repo test.