Self-hosted AI code documentation

Your codebase,
documented.
Your infrastructure.

Bring the complete DocuWriter platform into your environment. Generate documentation, organize it in Spaces, and keep it current with Autopilot.

Discuss your deployment Explore the options

Private cloud or on-premise. Scoped to your team.

Deployment architecture
Customer infrastructure

Private repositories

Your connected codebases

DocuWriter runtime

Generate · Manage · Maintain

Spaces + search

Shared codebase knowledge

AI connection

AI provider

Approved provider

Illustrative architecture Deployment and AI provider connections are agreed during scoping.

Your infrastructure

Application, database, and documentation in your environment.

Your AI connection

A supported provider path agreed with your security team.

One documentation platform

Generate, manage, and maintain knowledge across your codebase.

The complete platform

Private deployment.
A shared understanding.

Give engineering teams the documentation they need, in the environment your organization chooses. From the first repository import to the next code change.

01

Generate

Turn repositories into a complete picture.

Document architecture, services, APIs, dependencies, and the implementation behind them. Cover a single repository or a system spanning many.

Explore full-codebase documentation
02

Manage

Give your team a shared source of understanding.

Organize documentation in Spaces. Search, edit, and collaborate across the knowledge your team needs for onboarding, handovers, and everyday engineering.

Explore Spaces
03

Maintain

Keep the knowledge moving with the code.

Autopilot identifies documentation affected by code changes and prepares suggested updates for your team to review and apply.

Explore Autopilot

Choose your AI connection

Your infrastructure.
An AI path you can approve.

Where DocuWriter runs and where AI inference happens are separate decisions. Choose the connection that fits your vendor agreements and data requirements.

Your account · your provider

Customer-owned AI

Connect to a supported AI provider account controlled by your organization, with the provider relationship under your contracts.

  • Your provider credentials and usage limits
  • AI usage billed through your account
  • Models and network path reviewed together
Discuss your provider setup
Agreed service · defined scope

Managed AI connectivity

Discuss a managed AI service for your private deployment, with connectivity and data requirements agreed before implementation.

  • A defined provider and data flow
  • Usage and commercial terms in your quote
  • Operations and support scoped with your team
Discuss managed connectivity

Need a fully offline or air-gapped environment? Models, embeddings, updates, and support require a separate technical review. Let’s map the requirements

From requirements to rollout

Bring your constraints.
We’ll map the deployment.

A useful first conversation starts with your environment. Bring your engineering, platform, or security team. We’ll work through the decisions together.

Start a deployment review
  1. 01

    Map your environment

    Repositories, languages, network access, and where DocuWriter will run.

  2. 02

    Agree the data boundaries

    AI connectivity, storage, search indexes, identity, access, and retention requirements.

  3. 03

    Define the rollout

    Scope, implementation, updates, support, and a quote for your deployment.

A few practical details

Before you
bring it in-house.

Clear answers for the people reviewing your deployment.

What is included in the DocuWriter platform?

DocuWriter is an AI-powered platform for creating, updating and managing complete, structured documentation for entire codebases. Teams can connect repositories and generate documentation covering architecture, modules, services, classes, functions, dependencies, APIs, diagrams, READMEs, and other technical components. It supports both individual repositories and larger multi-repository systems.

Is self-hosted the same as fully offline?

No. Hosting DocuWriter in your infrastructure and choosing where AI inference runs are separate decisions. AI requests use the provider connection agreed for your deployment. Fully offline or air-gapped environments require a separate technical review of models, embeddings, updates, and support.

Can we use our own AI provider account?

Yes. Customer-owned AI is a deployment option. We review your supported provider, required models, credentials, network path, and usage requirements during scoping. Provider usage and billing stay under your account unless a managed service is agreed separately.

Where does our documentation live?

In a customer-hosted deployment, the application, database, users, and documentation run in your infrastructure. Spaces organize the documentation for search, editing, and collaboration. We agree storage, access, retention, and export requirements as part of the deployment review.

Can DocuWriter connect to private repositories?

Private repository access is part of deployment scoping. We review your Git provider, credentials, and network requirements, including self-hosted Git, VPNs, firewalls, and allowlists. Any custom integration work is agreed before implementation.

How is a self-hosted deployment priced?

Self-hosted deployments are quoted for your environment and scope. The review covers the software license, implementation, AI connectivity, and any additional integration or support requirements. Your team receives a defined scope and quote before proceeding.

Built around your environment

Your code holds the knowledge.
Put it to work for your team.

Complete codebase documentation. A deployment that fits.

Discuss your deployment Explore the full platform