FinalDocFinalDoc
Pricing
Enterprise

Private AI for Documentation: Why BYOK Matters

March 10, 2026 ยท 4 min read

Private AI for Documentation: Why BYOK Matters

AI-powered documentation is transformative. AI-powered documentation that sends your proprietary content to a third-party API is a security risk.

Your knowledge base contains sensitive information: unreleased product features, internal architecture, customer-facing APIs, security implementations, pricing strategies, and competitive positioning. When you use AI features โ€” writing assistance, chatbot, search, content analysis โ€” that content needs to go somewhere for processing.

The question is: where?

The Problem with Shared AI

Most AI-powered tools use a shared API key. Your content goes to OpenAI, Anthropic, or Google's servers. It's processed alongside content from thousands of other customers. The AI providers have policies about not training on API data โ€” but policies aren't the same as guarantees.

For many teams, this is fine. For enterprises in regulated industries โ€” healthcare, finance, government, defense โ€” it's a dealbreaker.

Common objections we hear:

BYOK: Bring Your Own Key

FinalDoc's Private AI feature lets you Bring Your Own Key. Instead of using FinalDoc's shared AI infrastructure, you point FinalDoc to your own AI endpoint. Your content never leaves your cloud.

We support three deployment models:

Azure OpenAI

Deploy GPT-4o on your own Azure subscription. You control the region, the data retention policy, and the network access. FinalDoc sends requests to your Azure endpoint โ€” Microsoft's enterprise data protection guarantees apply.

AWS Bedrock

Use Claude or other models through AWS Bedrock in your AWS account. Data stays in your VPC. IAM policies control access. CloudTrail logs every API call.

Custom Endpoint

Running a self-hosted model? Ollama, vLLM, or any OpenAI-compatible API? Point FinalDoc to your endpoint. We send standard OpenAI-format requests โ€” any compatible server works.

What Uses AI

Understanding which features send content to AI is important for your security review. Here's the full list:

FeatureWhat's SentWhy
Ved AI WriterSelected text + actionImprove, shorten, translate, etc.
Reader ChatbotUser question + relevant article chunksRAG-powered Q&A
Semantic SearchSearch queryGenerate embedding vector
Content HealthArticle textQuality scoring
Doc AutopilotCode file contentsGenerate documentation
TranslationArticle contentTranslate to target language
Diagram GenerationText descriptionGenerate Mermaid/diagram code
Design AssistantStyle descriptionGenerate theme CSS
Video StudioArticle textGenerate voiceover script
Article AudioArticle textText-to-speech conversion

With BYOK, every one of these goes to your endpoint instead of ours.

Setup

Configuration takes under 5 minutes:

  1. Go to Settings โ†’ AI Configuration
  2. Switch from "FinalDoc AI (Cloud)" to "Your Private Cloud"
  3. Select your provider (Azure OpenAI, AWS Bedrock, or Custom)
  4. Enter your endpoint URL and API key
  5. Click "Test Connection" โ€” FinalDoc sends a test prompt and verifies the response

Once configured, all AI features use your endpoint. No code changes. No migration. Every feature works exactly the same โ€” the only difference is where the processing happens.

What About Embeddings?

Semantic search uses vector embeddings (text-embedding-3-small, 1536 dimensions). These embeddings are stored in your FinalDoc database. With BYOK, the embedding generation also goes through your endpoint.

If you're using Azure OpenAI, deploy the text-embedding-3-small model alongside GPT-4o. For AWS Bedrock, use Amazon Titan Embeddings. For custom endpoints, any embedding model that returns 1536-dimension vectors works.

Enterprise Plan

Private AI (BYOK) is available exclusively on the Enterprise plan. This plan also includes SSO, IP restrictions, unlimited projects, and 50,000 AI credits/month.

See pricing or contact us for an Enterprise quote.

โ† Back to Blog