Per-Knowledge-Base Pricing

Master this essential documentation concept

Quick Definition

A pricing model where costs are charged for each separate knowledge base created, rather than per user or per feature.

How Per-Knowledge-Base Pricing Works

graph TD A[Organization Documentation Needs] --> B{How Many Knowledge Bases?} B --> C[KB 1: Product A Docs] B --> D[KB 2: Internal HR Wiki] B --> E[KB 3: API Reference] B --> F[KB 4: Client Portal] C --> G[Cost: $X per KB] D --> G E --> G F --> G G --> H[Total Monthly Cost: 4 x $X] H --> I{Compare to Alternatives} I --> J[Per-User Model: Cost x 50 Users] I --> K[Per-Feature Model: Cost x Features] I --> H H --> L[Predictable Budget Allocation] L --> M[Scale by Adding KBs] M --> N[New Product Launch = +1 KB = +$X]

Understanding Per-Knowledge-Base Pricing

Per-Knowledge-Base Pricing is a documentation platform billing structure that charges organizations based on the number of independent knowledge bases they operate, rather than the number of users accessing them or specific features enabled. This model has gained traction among documentation teams managing multiple products, client portals, or departmental wikis simultaneously.

Key Features

  • Each knowledge base is treated as a discrete, billable unit with its own content, settings, and access controls
  • Costs scale horizontally with the number of documentation hubs, not vertically with team size
  • Each knowledge base typically includes its own domain or subdomain configuration
  • Independent versioning, theming, and permission structures per knowledge base
  • Flat-rate pricing per knowledge base makes budgeting straightforward and predictable

Benefits for Documentation Teams

  • Large teams with many contributors can access a single knowledge base without inflating per-user costs
  • Encourages clean separation of documentation for different products or audiences
  • Startups and small teams can maintain professional multi-product documentation affordably
  • Easier cost allocation across departments or client accounts when each has its own knowledge base
  • Scales naturally as product lines grow, with clear cost implications per new documentation hub

Common Misconceptions

  • It does not mean unlimited users — some platforms combine per-knowledge-base pricing with user tier limits
  • More knowledge bases does not always mean better organization; consolidation may be more efficient for some teams
  • Per-knowledge-base pricing is not inherently cheaper than per-user pricing — the best model depends on team size and documentation scope
  • A knowledge base is not the same as a single article or category; it is an entire documentation site or portal

Real-World Documentation Use Cases

SaaS Company Managing Multiple Product Documentation Sites

Problem

A software company with five distinct products needs separate, branded documentation portals for each. Under per-user pricing, their 80-person team would face enormous costs, even though only 5-10 writers actively contribute to each product's docs.

Solution

Adopt a per-knowledge-base pricing model to create five independent knowledge bases — one per product — paying a flat rate for each rather than scaling costs across all 80 team members.

Implementation

1. Audit all existing documentation to identify natural product boundaries. 2. Map each product to a dedicated knowledge base with its own subdomain. 3. Assign relevant writers to each knowledge base. 4. Calculate total cost as number of products multiplied by per-KB rate. 5. Review quarterly as new products launch.

Expected Outcome

Documentation costs become predictable and proportional to product count, not headcount. Adding a sixth product simply adds one knowledge base cost, making budget planning straightforward.

Agency Creating Client-Specific Documentation Portals

Problem

A documentation agency builds and maintains help centers for 12 different client companies. Charging per user would be complex since each client has varying team sizes, and the agency needs clean separation between client content.

Solution

Use per-knowledge-base pricing to create one knowledge base per client, billing clients individually based on their dedicated documentation hub while keeping all content fully isolated.

Implementation

1. Create a separate knowledge base for each client during onboarding. 2. Configure unique branding, domains, and access controls per KB. 3. Pass the per-KB cost through to client invoices for transparent billing. 4. Archive or delete KBs when client contracts end. 5. Track active KBs monthly for accurate cost reporting.

Expected Outcome

Clean client separation, transparent cost pass-through, and a scalable agency model where revenue and costs both grow linearly with the number of active client engagements.

Enterprise Separating Internal and External Documentation

Problem

A mid-size enterprise needs distinct documentation environments: a public-facing customer help center, an internal employee handbook, a technical API reference for developers, and a partner onboarding portal — each with different audiences and access rules.

Solution

Implement per-knowledge-base pricing to maintain four purpose-built knowledge bases, each configured for its specific audience, without paying for hundreds of internal users under a per-seat model.

Implementation

1. Define the four audience segments and their documentation needs. 2. Provision a knowledge base for each audience type. 3. Set public vs. private access controls per KB. 4. Assign content ownership teams to each KB. 5. Review KB consolidation opportunities annually to avoid unnecessary costs.

Expected Outcome

Each audience receives a tailored documentation experience with appropriate access controls, while total documentation costs remain fixed at four knowledge base fees regardless of how many employees or customers access the content.

Open Source Project Maintaining Versioned Documentation Hubs

Problem

An open source project needs to maintain active documentation for three major supported versions of their software simultaneously. Users on older versions must access accurate, version-specific documentation without confusion.

Solution

Create one knowledge base per supported major version under per-knowledge-base pricing, allowing the community to maintain version-accurate docs without paying per contributor in a large open source community.

Implementation

1. Identify the number of actively supported software versions. 2. Create a dedicated knowledge base for each version. 3. Clearly label each KB with version numbers in the domain or title. 4. Allow community contributors to access relevant KBs without user-count cost penalties. 5. Deprecate and archive KBs when versions reach end-of-life.

Expected Outcome

Users find accurate version-specific documentation easily, contributors can participate freely without inflating costs, and the project maintainers pay only for the number of active version hubs maintained.

Best Practices

✓ Audit Before You Create: Map Knowledge Bases to Real Audiences

Before provisioning knowledge bases under a per-KB pricing model, conduct a thorough audit of your actual documentation audiences and content domains. Creating too many knowledge bases inflates costs unnecessarily, while too few creates confusing, mixed-audience content.

✓ Do: Define a clear audience or product boundary for each knowledge base before creating it. Ask whether a distinct URL, branding, or access control is genuinely needed.
✗ Don't: Don't create separate knowledge bases for topics that could logically live as categories or sections within a single hub. Avoid the temptation to over-separate content just because the pricing model allows it.

✓ Establish a Knowledge Base Governance Policy

With per-knowledge-base pricing, the number of KBs directly impacts your monthly bill. Establish a formal governance policy that defines who can request a new knowledge base, what criteria must be met, and who approves the creation.

✓ Do: Create a simple intake form or checklist that teams must complete to justify a new knowledge base. Include criteria like audience size, content volume, and access control requirements.
✗ Don't: Don't allow individual team members or departments to spin up new knowledge bases without central approval. Uncontrolled KB proliferation leads to budget overruns and fragmented documentation strategies.

✓ Align Knowledge Base Boundaries with Billing and Cost Centers

One of the strongest advantages of per-knowledge-base pricing is the ability to allocate documentation costs clearly across business units. Structure your knowledge bases to mirror your organization's cost centers or client accounts for clean financial reporting.

✓ Do: Map each knowledge base to a specific budget owner, department, or client. Use this structure to produce monthly cost reports that show exactly what each team or client's documentation hub costs.
✗ Don't: Don't create knowledge bases that span multiple departments or clients without a clear cost allocation plan. Shared KBs obscure accountability and make chargeback or client billing difficult.

✓ Review and Retire Inactive Knowledge Bases Regularly

Per-knowledge-base pricing means you pay for every active KB, including ones that may have become outdated or redundant. Schedule quarterly reviews to assess whether all active knowledge bases are still earning their cost.

✓ Do: Set a quarterly calendar reminder to review KB usage analytics. Archive or consolidate knowledge bases for discontinued products, completed projects, or deprecated software versions.
✗ Don't: Don't let knowledge bases accumulate passively. Paying for a KB with zero monthly visitors or no recent updates is a direct, avoidable cost drain under per-KB pricing models.

✓ Forecast Knowledge Base Growth When Evaluating Pricing Models

Per-knowledge-base pricing is most cost-effective when your team is large relative to your number of documentation hubs. Before committing to this model, project your knowledge base count over 12-24 months to ensure the pricing remains favorable as you scale.

✓ Do: Build a simple spreadsheet comparing per-KB pricing against per-user pricing at your current and projected team sizes and KB counts. Include growth scenarios for new product launches or client acquisitions.
✗ Don't: Don't assume per-knowledge-base pricing is always cheaper than alternatives. For organizations with very few KBs but small teams, per-user pricing may actually be more economical.

How Docsie Helps with Per-Knowledge-Base Pricing

Book a Demo

Build Better Documentation with Docsie

Join thousands of teams creating outstanding documentation

Book a Demo