Self-Hosting Draft: Keep Your Code Private

Why Self-Hosting Matters

Many teams cannot send their codebase to third-party services. Regulatory requirements (SOC 2, HIPAA, GDPR), intellectual property protection, and internal security policies all demand that code stays on infrastructure you control. This is not an edge case — it is the default for most enterprise engineering teams.

Most AI coding tools require sending your code to external servers for processing. Draft takes the opposite approach.

How Draft Self-Hosting Works

Draft is designed from the ground up to run on your own infrastructure. The self-hosted version has full feature parity with the cloud version — there is no premium tier that requires sending code externally.

Getting started takes two commands:

git clone https://github.com/doramirdor/draft
docker compose up

Draft connects to AI providers (Claude, GPT, etc.) through your own API keys. All orchestration — task planning, agent coordination, merge verification — happens locally. The AI providers only see the specific code snippets that agents need to process, not your entire repository.

Architecture for Privacy

Draft's architecture separates orchestration from execution. The orchestration layer (task planning, dependency resolution, merge management) runs entirely on your infrastructure with zero external calls. Only the AI agent execution layer communicates with external APIs, and only with the minimal context each agent needs.

This means your repository structure, file layout, git history, environment variables, and configuration files never leave your network. Agents receive isolated task descriptions and file snippets, not repository-wide access.

Deployment Options

Draft runs anywhere Docker runs: your laptop, an EC2 instance, a Kubernetes cluster, or an air-gapped server. For teams with strict compliance requirements, Draft can be configured to route all AI traffic through a VPN or private endpoint. For teams that need no external AI calls at all, Draft supports local model backends.

The Principle

For teams that need complete control over their development infrastructure, self-hosting is not an afterthought — it is the primary deployment model. Your code, your servers, your rules.