Classify your data, pick one of four deployment patterns, own the knowledge layer, and set governance before you buy a single GPU.

Private AI for business means using AI on your company's documents and data under terms and infrastructure you control: who can see the data, where it is processed, how long it is kept, and whether it is used for training. It ranges from a vendor API with no-training contracts to open models running in your own VPC or data center. For most companies, the right first move is not buying GPUs. It is owning the knowledge layer (the docs, SOPs, and specs the AI reads) in a system you control, and keeping the model provider swappable behind clear contracts and admin controls.
Key takeaways
If you are new to the concept, start with our overview of private AI. This guide is the implementation plan: classify data, choose a deployment pattern, consolidate knowledge, set access, pilot, and scale.
| Step | What you decide | Output |
|---|---|---|
| 1. Classify data | Which data can go to which kind of AI | A four-tier classification table |
| 2. Choose a deployment pattern | Vendor API, cloud model service, VPC-hosted, or on-prem | One default pattern per data tier |
| 3. Build the knowledge layer | Where company knowledge lives and who owns it | A consolidated, self-hosted or controlled workspace |
| 4. Access and governance | Identity, roles, AI on/off, key ownership | An AI usage policy and admin settings |
| 5. Pilot and scale | Who goes first and how you measure it | A 30/60/90-day rollout |
Before you compare vendors, decide what data the AI will touch. Most companies already have some version of a classification policy. If you do not, this four-tier template is enough to start.
| Tier | Examples | Acceptable AI pattern |
|---|---|---|
| Public | Published docs, marketing pages, public pricing, open-source code | Any reputable AI tool, including consumer tools |
| Internal | SOPs, meeting notes, internal wikis, project plans, org charts | Vendor API or business plan with no-training terms and a signed data processing agreement |
| Confidential | Customer notes, contracts, roadmaps, unreleased product specs, financials | Dedicated cloud model service in your own cloud account, or VPC-hosted models; vendor API only if retention and region terms are reviewed and approved |
| Restricted | Credentials, regulated personal data, health or payment data, M&A material, legal privilege | No AI by default; if required, self-hosted or VPC-hosted models with a documented exception |
Two practical rules make this table work:
There are four common patterns for private AI solutions. They differ mainly in how much control you get over data and how much operational work you take on. For the technical detail on each (serving stacks, model choices, hardware), see our guide to private LLMs.
| Pattern | Data control | Ops burden | Time to start | Cost drivers | Best for |
|---|---|---|---|---|---|
| (a) Vendor API or business plan with no-training terms | Contractual: vendor processes data under its terms | Low | Days | Per-seat or per-token pricing | Startups and small teams; Public and Internal data |
| (b) Dedicated cloud model service in your cloud account | Contractual plus your cloud's controls (region, network, IAM) | Low to medium | Days to weeks | Tokens or provisioned throughput, cloud networking | Mid-size and enterprise teams already on AWS, Azure, or Google Cloud; Confidential data |
| (c) Open models hosted in your private cloud or VPC | High: you run the model in infrastructure you control | Medium to high | Weeks | GPU instance hours, storage, engineering time | Enterprises with ML or platform teams; Confidential and some Restricted data |
| (d) Self-hosted open models on-prem | Highest: data never leaves your facilities | High | Weeks to months | Hardware purchase, power, maintenance, staff | Regulated or air-gapped environments; Restricted data |
The four deployment patterns trade operational effort for data control. Most companies start in the lower-left and move right only for specific workloads.
Patterns (a) and (b) depend on the vendor's commitments, so read them yourself rather than relying on sales summaries. As of October 2026, the vendors' own pages state:
Note the phrase "by default" in several of these. Your security review should confirm which plan you are on, which settings are enabled, and which features (such as logging for abuse monitoring or caching) have their own retention rules.
A reasonable default for private AI for startups and mid-size companies: pattern (a) for Internal data, pattern (b) for Confidential data, and no AI for Restricted data until you have a clear use case. Enterprise private AI programs often add pattern (c) later for specific workloads where cost at volume or data residency justifies the engineering effort. Pattern (d) is usually driven by regulation or contracts, not preference. If you are weighing self-hosting broadly, our self-hosted AI guide covers the trade-offs. If regulation is the driver, read what data sovereignty means for business tools to separate data residency from legal control.
The key point: the model layer is the part most likely to change. Prices, model quality, and terms move every few months. Make sure nothing in your plan locks your knowledge to one model provider.
An AI assistant's answers are only as good as the documents it can read. If your SOPs live in five tools, half your specs are out of date, and nobody knows which wiki page is current, a private model will give confident answers drawn from stale material. Our guide to building an AI knowledge base covers how to prepare and test that content.
The most useful work in a private AI rollout is usually consolidation, not model selection:
We cover the content side in more depth in our guide to building an internal AI knowledge base.
AFFiNE is an open-source, local-first workspace that combines docs, whiteboards (an edgeless canvas), and databases. You can use AFFiNE Cloud or self-host AFFiNE as your knowledge base. The official self-hosting path is Docker Compose (install docs). When self-hosted, your data stays in your own PostgreSQL, Redis, and file storage (local disk, S3-compatible storage, or Cloudflare R2).
This matters for private AI because the knowledge layer and the model layer stay separate. Your documents live in infrastructure you run. The AI provider is a setting, not a migration. AFFiNE also includes an MCP server, so AI clients you approve can search and read workspace content through a defined interface, with read-only credentials by default. Because AFFiNE is local-first, docs and whiteboards remain editable offline in the desktop app and sync later. That applies to editing, not to AI features, which need a connected provider.
A private AI program fails security review when nobody can answer "who can see what, and which AI can read it." Settle these controls before the pilot.
copilot.byok.allowCustomEndpoint) and, as a separate setting, endpoints on private networks (allowPrivateEndpoint). That makes it possible to point AFFiNE at a model server you operate, for example one serving open models in your VPC. Feature coverage depends on the model and must be tested per model; it is not guaranteed. AFFiNE does not run models itself, and native local model support is an open community feature request.Publish a one-page policy employees can actually follow. It should answer:
A 30/60/90-day plan: agree on data tiers and the knowledge layer first, pilot on Internal data, then scale.
| Phase | Goals | Key deliverables | Owner |
|---|---|---|---|
| Days 1-30: Foundation | Agree on data tiers and default patterns; pick the knowledge layer | Classification table; approved pattern per tier; draft AI usage policy; workspace deployed with SSO | IT/security lead with a knowledge owner |
| Days 31-60: Pilot | Prove value with one or two teams on Internal data | Consolidated docs for the pilot teams; AI enabled for pilot workspaces only; provider keys under company ownership; feedback on answer quality | Pilot team leads |
| Days 61-90: Scale | Expand to more teams and, if approved, Confidential data | Final AI usage policy; vendor reviews complete; per-workspace AI settings documented; training for new teams; a list of docs to fix | IT, security, and department heads |
Good pilot candidates are teams with heavy, repeated questions against stable docs: support, onboarding, internal IT, and engineering runbooks. Measure what you can observe directly, such as how often the assistant answers from the right document and how many docs had to be fixed, rather than relying on vendor productivity claims.
We will not quote a number, because costs depend heavily on usage and pattern. Build your estimate from these categories:
Use this 10-question checklist for any private AI vendor, including AI features inside tools you already use:
AFFiNE is a good fit when you want to own the knowledge layer: a self-hosted workspace with docs, whiteboards, and databases, data in your own Postgres and storage, OIDC SSO, workspace roles and per-document access, and optional AI with company-owned provider keys. It suits teams that want to keep the model provider swappable and decide per workspace whether AI is on.
For larger deployments and licensing questions, see AFFiNE for enterprise or book a demo. To see how AI works inside the workspace, visit AFFiNE AI.
It is the use of AI on company data under terms and infrastructure you control. That can mean a vendor API with contractual no-training and retention terms, a model service in your own cloud account, or open models hosted in your VPC or data center. The common thread is that you can answer where data goes, who can see it, and how long it stays.
Usually yes, in its lightest form. A small business rarely needs its own GPUs. It does benefit from a business plan with no-training terms, a short usage policy, and one controlled home for its documents. That costs little and closes the most common leak: employees pasting company data into personal accounts.
You can use OpenAI's business offerings under stronger terms than consumer accounts. OpenAI states that for ChatGPT Business, Enterprise, Edu, and its API Platform, it does not train on business data by default (OpenAI enterprise privacy). Data is still processed by OpenAI, so confirm the retention settings for your plan and decide which data tiers it is approved for.
A focused rollout using vendor APIs or a cloud model service can reach a working pilot within about 30 days and a broader rollout in about 90 days, as in the plan above. Self-hosting models on your own hardware usually takes longer because of procurement and setup. The document consolidation work often takes longer than the AI setup.
Most companies do not. GPUs make sense when regulation or contracts require that data never leaves your facilities, or when your volume is high enough that owning capacity is cheaper than paying per token. Start with a managed pattern and revisit the decision once you have real usage data.
Credentials and secrets, regulated personal data (such as health or payment data), legally privileged material, and anything your contracts forbid sharing with third parties. Treat these as the Restricted tier: no AI by default, and only a documented exception using a pattern you fully control.
Self-host free up to 10 seats; Team $10/seat/month billed annually; offline Installable License via sales.