What a knowledge base costs when you build, partner or subscribe
The software license is usually the smallest line in a self-hosted knowledge base budget. The total depends on hosting, administration, migration, support and identity integration, and on how many people edit and read the wiki. BookStack is released under the MIT license and XWiki Standard under the LGPL 2.1, so neither charges a per-user license fee. Outline is different: it is licensed under the Business Source License 1.1, and its additional use grant forbids offering it as a commercial Document Service, so a company should have its counsel confirm that its intended use fits before budgeting around it. XWiki Pro and XWiki SAS support subscriptions add a recurring fee, and XWiki SAS states that cloud and on-premises pricing is the same across its Starter, Basic, Business and Enterprise tiers, each tied to a user ceiling. Ask the vendor for the tier that matches your headcount today and at the growth point you plan for.
For a reference point, Notion's pricing page, as read in October 2026, lists Plus at $10 and Business at $20 per member per month, with Enterprise by quote. SAML SSO starts on the Business plan and SCIM provisioning is Enterprise only. Multiply those figures by your member count and by twelve to see the recurring SaaS line, then compare it with the self-hosted items that recur: server and backup capacity, patching and upgrades, and the administrator hours to run them. One-time items include the initial installation, migrating content from Confluence or Notion, and configuring SSO. XWiki SAS lists consulting at 1200 EUR per day, which requires a Business or Enterprise support plan, and its Confluence Migrator Pro is priced from 2000 EUR. These figures come from the cited pages and may have changed, so confirm them before you use them in a comparison.
The comparison works best as a five-year total, with each line assigned to an owner: your team, an implementation partner or the vendor. Ask any partner for a written quote that separates fixed-scope work (installation, SSO, migration, hardening) from recurring work (support, upgrades, backups) and states what is excluded, such as content cleanup or training. Ask whether your Confluence spaces, page history and attachments will be migrated and what the migration tool does not keep. Your cost model should also reflect how often your organization will read the wiki during an incident, since hosting that stays reachable during outages can add infrastructure cost. Treat the self-hosted figure as an estimate until those items are priced.
Cost components for in-house, partner and SaaS delivery
This table compares the cost lines of running a knowledge base yourself, with an implementation partner, or on a per-member SaaS workspace. Read each row for who pays, whether the cost is one-time or recurring, and what moves it up or down. The main takeaway is that free wiki software shifts cost into labor, hosting and support rather than removing it.
| Cost component | In-house build | Partner delivery | Per-member SaaS |
|---|---|---|---|
| Software license | Free for BookStack (MIT) and XWiki Standard (LGPL 2.1); confirm terms for any add-on you install | Same open-source license, paid to the partner only for services | Per-member fee, such as Notion Business at $20 per member per month (Notion pricing page); recurs |
| Support subscription | Optional; you staff internal expertise instead | Optional vendor subscription, for example XWiki SAS Business or Enterprise support, which the company ties to consulting access; recurs | Included in the subscription; check what tier unlocks SSO and provisioning |
| Migration tooling | Your staff script exports and imports; tooling cost is labor | Partner quotes tooling and labor; Confluence Migrator Pro from XWiki SAS is priced from 2000 EUR, with a trial limited to 30 pages per migration (XWiki Store); one-time | Vendor import tools or partner scripts; confirm what history, permissions and attachments carry over |
| Consulting and training days | Internal staff time to learn the platform | Consulting at 1200 EUR per day and training at 1500 EUR per day from XWiki SAS (xwiki.com pricing); one-time unless retained | Usually limited to vendor onboarding; confirm whether paid services exist |
| Identity integration | Internal effort to configure SSO and directory groups; one-time plus change work | Partner configures SAML, OIDC or LDAP and tests; one-time, with later changes billed | SAML SSO starts on Business; SCIM provisioning is Enterprise only (Notion pricing page); recurs with the plan |
| Hosting and infrastructure | Your servers or cloud accounts, databases, storage and networking; recurs | Often the same, hosted in your accounts; partner labor is separate; recurs | Included in the fee; you control less of data location and backup |
| Administration and upgrades | Internal staff patch, upgrade and monitor; recurs and grows with page count | Retainer or per-task support covers upgrades and fixes; recurs | Vendor-managed; confirm release notice and downtime terms |
| Backup and restore testing | Internal backups and periodic restore tests; recurs | Partner can design and test restores; one-time setup plus recurring tests | Vendor backup and export features; confirm retention and your own export rights |
| Per-member SaaS fees | None | None, unless the partner resells a SaaS tier | Recurs for every licensed member, including guests and leavers until removed |
Which knowledge base costs are one-time and which recur
The one-time costs are the work that gets a wiki to its first working state: installation, configuration, identity integration, migration of existing content, and the initial structure of books, chapters and spaces. When you buy this from a partner, you pay for that work against a written scope. When your own staff do it, the cost is their time, which is easy to undercount. Migration is the item most often underestimated. If you move from Confluence, confirm with any tool vendor or partner which content survives the move (spaces, pages, users, groups, permissions, attachments, page history and attachment history are not all carried over the same way) and price the cleanup of stale or duplicate pages separately. The migration tool itself may carry its own license fee. XWiki SAS, for example, lists Confluence Migrator Pro at a price from 2000 EUR, and that figure should be checked against the current store listing before you budget.
The recurring costs are the ones that keep the wiki safe and readable after launch: hosting, patching, backups and restore tests, administration of accounts and permissions, search tuning, and any support subscription. Per-member SaaS fees are the recurring line in the other direction, and they scale with headcount rather than with infrastructure. Upgrade effort is the recurring item most teams leave out. BookStack publishes official installation scripts for Ubuntu releases but no official Docker images, so your team either maintains a community container setup or runs the scripted install and owns each upgrade. XWiki publishes a stable line and LTS lines, and the choice between them changes how often you upgrade and how much testing each upgrade needs. Ask any partner to quote upgrade and patching as a separate, annual line item, and to state which XWiki or BookStack release line they will support.
Before you compare totals, decide which recurring lines you will pay for and which your staff will absorb. A free license does not mean zero running cost, and a support subscription does not replace an internal owner who approves changes. Ask every bidder to split its quote into one-time work, first-year recurring items and later-year recurring items, and to name the person or team responsible for each. Verify any SaaS per-member price on the vendor's current pricing page, because the tier that includes SSO or user provisioning may not be the cheapest one.
What moves the knowledge base cost up or down
The licence line is rarely the largest cost of a self-hosted wiki. The main drivers are how many people need access, how much content must move, which identity and Pro features are required, where the data must live, and how much operating skill your team already has. Each card below is a lever you can check before asking for a quote.
User count and XWiki Pro tiers
XWiki Pro and support subscriptions are sold in tiers defined by user count: Starter for up to 25 users (XWiki Cloud only), Basic for up to 1,000 users, Business for up to 10,000 users and Enterprise for unlimited users. XWiki SAS states that cloud and on-premises pricing is the same. Ask the vendor which tier your headcount, including contractors and external readers, falls into, and whether read-only users count.
Page volume and attachments
Migration cost scales with the number of spaces, pages, users, groups, permissions and attachments. Confluence Migrator Pro keeps page history but not attachment history, so teams that rely on old attachment versions for audit need a separate archive plan. Inventory page counts and attachment storage before the quote, and ask the partner how much of the work is scripted versus manual cleanup of broken links and macros.
Identity integration and Pro features
SAML, OIDC and LDAP sign-in are where configuration effort concentrates, and some identity and collaboration connectors sit in XWiki Pro rather than the free Standard edition. Confirm which directory you run, whether group mapping must drive page permissions, and which connectors you need, such as Active Directory, Azure Active Directory or office suite connectors. Each feature that moves into Pro changes the subscription line.
Hosting location and retention
Where the wiki runs changes who is paid for what. Self-hosting shifts infrastructure, backups, patching and monitoring onto your team or a partner, while SaaS bundles those into a per-member fee. Regulated retention adds cost in the form of longer backups, immutable copies and audit logging. For example, a broker-dealer must keep certain business communications for at least three years, so check whether wiki content falls under a retention rule before you choose storage.
Customization and Pro applications
Custom macros, templates, theme work and bespoke connectors are one-time build costs that recur whenever the platform is upgraded and the custom code is retested. Pro applications such as diagrams, forms, calendars and ideas reduce custom development but add subscription fees. Ask for a written list of customizations, who owns the code, and how each item is covered during upgrades.
In-house PHP or Java skills
Operating cost depends on the stack. BookStack requires PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later, while XWiki runs on Tomcat with MySQL, PostgreSQL or MariaDB. If your team already runs one of these, administration stays internal. If not, budget for a partner retainer or support plan. Also confirm who handles security patches, since BookStack publishes no official Docker images and points to community setups.
How the cost profile differs by platform
BookStack is released under the MIT license, so the software itself carries no license fee and you can run it in your own infrastructure without a per-member charge. Its cost sits in hosting, the PHP and database stack, and the people who keep it patched and backed up. The project publishes official installation scripts for Ubuntu 26.04, 24.04 and 22.04, but it does not publish official Docker images and points to community Docker setups instead, so a container-based deployment means choosing and trusting a third-party image.
- Licensing: MIT permits commercial use, modification and internal redistribution without a per-user fee. Confirm that your legal team accepts the terms for your use case.
- Support purchase: Paid support plans and sponsorship are available from the project. Ask what a plan covers, response expectations and whether it includes upgrade assistance.
- Runtime requirements: PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later. Your platform team carries the operating system, database and PHP patching.
- Admin effort: Expect recurring effort for updates such as v26.09.1, backups, SSO configuration (OIDC, SAML2 or LDAP) and enforcing multi-factor authentication by role.
- Partner scope: If you hire an implementation partner, quote the installation, identity integration, content migration and runbook handover as separate line items.
Before you commit, confirm which support tier you need, who owns the community container image you deploy and how often your team will perform upgrades.
XWiki Standard is the free open source edition under the LGPL 2.1, so the core platform has no license fee. The cost decision comes when you consider the paid layers: XWiki Pro adds business applications, connectors and SAS support, and support subscriptions come in Starter, Basic, Business and Enterprise tiers. XWiki SAS also sells consulting and training by the day, and states that cloud and on-premises pricing is the same. Consulting requires a Business or Enterprise support plan.
- Licensing: LGPL 2.1 for the platform and official Docker images, so the free edition can be deployed without a license fee. Check the terms of any Pro application separately.
- Support tiers: Starter (up to 25 users, XWiki Cloud only), Basic (up to 1,000 users), Business (up to 10,000 users) and Enterprise (unlimited users). Match the tier to your user count and hosting model.
- Consulting and training: Consulting is listed at 1200 EUR per day and training at 1500 EUR per day. Ask for the number of days your scope needs and what is excluded.
- Migration: Confluence Migrator Pro is priced from 2000 EUR, and its trial is limited to 30 pages per migration. Confirm page history and attachment handling before you budget.
- Admin effort: Official images come in MySQL, PostgreSQL and MariaDB variants on Tomcat. Your team maintains the stable, LTS or intermediate LTS line it chooses.
Compare your user count against the tiers, then ask whether the Pro applications you need are included in the support plan you are quoting.
Outline is licensed under the Business Source License 1.1, not an open source license. Its additional use grant forbids using the software to offer a commercial Document Service, so the license terms need legal review before you choose it, especially if the wiki will be offered to customers or partners. For an internal wiki, the cost profile looks different from the other two options, and the license review is the first cost item to settle.
- Licensing: BSL 1.1 with an additional use grant that forbids offering a commercial Document Service. Ask counsel to confirm whether your intended use falls inside the grant.
- Latest release: Outline 1.11.0 was published on October 12, 2026. Check the release notes for hosting requirements before you plan the deployment.
- Support purchase: Do not assume a vendor support plan exists for your deployment model. Ask the vendor directly what commercial support is available for self-hosted use.
- Legal review cost: Counsel time is a one-time cost at the start of the project, and it can change the choice of platform if the terms do not fit.
- Admin effort: Expect recurring work for upgrades, identity integration and backups, as with any self-hosted wiki.
Before you select Outline, get a written view from legal on the additional use grant, then confirm the support options in writing before you request a quote.
How to build your own knowledge base cost estimate
This sequence turns an open-ended wish for a self-hosted wiki into a written, comparable cost model that covers software, people, hosting, migration and vendor support, so you can set it against a per-member SaaS figure at the same headcount.
Count named users and editors
Start by counting the people who will sign in and how many of them will write or approve pages, not only read them. Separate named readers, contributors and approvers, and note any external users such as contractors or customers who need access. Pull these numbers from your directory, not from memory, so the count matches what your identity system will actually provision. The step is done when you have one table with headcount per role, and the total matches your directory group export. This count drives per-member SaaS pricing and also decides which XWiki Pro or support tier you would need, since those tiers are sized by user count.
Inventory spaces, pages and attachments
Measure what you would move or create. Count the spaces or books, the approximate page count, the total attachment volume and whether page history must be kept. Ask a sample of content owners which pages are still current, because stale content inflates migration effort and storage without adding value. Record which spaces hold restricted material such as HR, legal or security pages, since those need separate permission models. The output is a content inventory with page counts, attachment sizes and a short list of spaces that need special handling. Use it later to size storage, estimate migration scope and decide what to archive instead of migrate.
Choose the platform and license tier
Shortlist platforms against your content structure, permission needs and license terms. BookStack is MIT licensed and suits a simpler book, chapter and page model. Outline's Business Source License 1.1 forbids offering a commercial Document Service, so read its additional use grant with counsel before committing. XWiki Standard is free and open source under LGPL 2.1, while XWiki Pro and support subscriptions are sold in Starter, Basic, Business and Enterprise tiers. Record the license, the tier and the features you need, such as SSO connectors or Pro applications. The step is complete when you have one selected platform and a written list of the tier features it requires.
List identity and migration needs
Document how users will sign in and how content will arrive. Note whether you need SAML, OIDC or LDAP sign-in, whether multi-factor authentication must be enforced by role, and how directory groups map to spaces. On the migration side, list each source system, the content types, whether users, groups and permissions must come across, and whether history is required. For Confluence sources, check the Confluence Migrator Pro scope, which keeps page history but not attachment history and is priced from 2000 EUR per the XWiki Store. Ask the vendor to confirm which of these needs their migration tooling covers. The output is a signed-off requirements list that the quote must address line by line.
Price hosting and administration hours internally
Estimate what you will pay to run the platform yourself. List the servers or containers, the database (BookStack requires PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later), backup storage, monitoring, TLS certificates and the expected admin time for patching, upgrades and user lifecycle work. Use your own internal rates and your own cloud or data center prices, since no universal figure applies to your environment. Separate one-time setup from recurring operations, and mark which items scale with users or content volume. The step is done when you have a monthly and annual internal run-cost sheet with every assumption written beside it, so a reviewer can change one input and see the effect.
Add support and consulting days from vendor quotes
Request written quotes for the work you cannot do internally. Ask the software vendor or partner for the support subscription tier, what response commitments it includes, and whether cloud and on-premises pricing are the same. For XWiki, the published consulting rate is 1200 EUR per day and requires a Business or Enterprise support plan, while training is listed at 1500 EUR per day, so confirm whether any days are bundled. Ask for the scope of installation, SSO configuration, migration, upgrade assistance and knowledge transfer, each with its own day count and deliverable. Ask whether any services are fixed-scope and how change requests are priced. The output is a line-item vendor quote you can compare directly with the internal estimate.
Compare against per-member SaaS at the same headcount
Build the SaaS side of the comparison using the same headcount from step one. Take the current per-member monthly price from the vendor's public pricing page, annualize it, and multiply by named users. For example, as an illustrative calculation only, a 100-member team at a given monthly seat price has an annual figure that equals seat price times 12 times 100, before any tier that adds SSO or provisioning features. Check which features sit behind higher tiers, such as Notion's SAML SSO on Business and SCIM provisioning on Enterprise, and add those tiers to the SaaS figure. Then place both totals side by side, with one-time costs, recurring costs and the three-year view, so the comparison reflects the same scope.
Confirm written quote terms before deciding
Before you choose a route, ask every vendor and partner to confirm the same set of terms in writing. Ask for the license terms that apply to the production version, the support tier and included hours, the upgrade policy and who performs upgrades, the data location and hosting options, exit and export terms, and how price changes are handled at renewal. Ask whether the quote is fixed-scope, what triggers a change order, and what the acceptance criteria are for migration. The step is complete when each quote answers the same checklist and the internal estimate has been reviewed against those answers. Keep this file with your requirements list so the decision can be audited later.
Why identity and permission work changes the price
Identity features are often where the price of a knowledge base moves most, so check them before comparing headline numbers. In SaaS, SAML SSO and SCIM provisioning frequently sit behind higher tiers. Notion's pricing page, as read in October 2026, places SAML SSO from the Business plan and SCIM provisioning on Enterprise only, which means a team that needs automatic joiner and leaver handling may pay for a tier well above the per-member rate it first compared. Self-hosted options change the arithmetic but do not remove the work. BookStack supports OIDC, SAML2 and LDAP sign-in and can enforce multi-factor authentication per role, and XWiki Pro lists Active Directory and Azure Active Directory SSO applications. Confirm with the vendor or XWiki SAS which of these features ship in your edition or tier, since licensing and feature lists change.
Budget for the identity work itself. Directory group mapping, meaning the rules that turn your LDAP, Active Directory or OIDC groups into wiki roles and space permissions, is usually a one-time configuration effort paid to an implementation partner or carried by your own identity team. Access audits recur. Someone must periodically confirm who can read HR, legal or security spaces, and that a departed employee no longer has access. Ask any partner to quote the group mapping design, the test plan for each role, and a reproducible report of effective permissions, and ask whether that report is a recurring deliverable or a one-time export.
Before signing, make the identity decisions explicit: which directory is the source of truth, how groups map to the roles in your permission model, whether deprovisioning is automated or manual, and which features your chosen tier requires. Treat a missing SCIM or group sync capability as a cost to price in, not a footnote. A partner should be able to show a written list of the identity features included in the quoted scope and the ones that need a paid edition, support plan or custom connector.
Questions buyers ask about knowledge base cost and effort
Is a self-hosted wiki free to run?
The software itself is free to download and use in most cases. BookStack is MIT licensed and XWiki Standard is the free open source version under LGPL 2.1, so the license fee is zero. The costs sit elsewhere: the servers or cloud accounts that host it, the database, backups, certificates, identity integration, and the staff time to administer it. Paid options such as XWiki Pro or support subscriptions add a recurring fee that scales with user tiers. Ask any partner to separate one-time setup costs from recurring hosting and administration costs in the quote.
How much effort does migrating from Confluence or Notion take?
Effort depends on how many spaces, pages, attachments, users and permission rules you have, and how clean that content is. XWiki SAS offers Confluence Migrator Pro, which moves spaces, pages, users, groups, permissions, attachments and metadata and keeps page history but not attachment history. It is priced from 2000 EUR per the XWiki Store listing, and its trial is limited to 30 pages per migration, so a test run on a sample is a useful first step. Plan for manual cleanup of broken links, macros and stale content, and confirm with any partner exactly which history and attachment versions will survive the move.
Can our team run the wiki ourselves after launch?
Yes, if you have people who can administer a web application, a database and an identity integration. BookStack requires PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later and provides official installation scripts for Ubuntu 26.04, 24.04 and 22.04. XWiki's official Docker images run on Tomcat with MySQL, PostgreSQL or MariaDB variants. The ongoing work includes applying upgrades, testing backups, managing extensions and monitoring. Ask whether your team can keep pace with security releases, and whether a support subscription or retainer is worth its recurring cost for your staffing level.
How long does a knowledge base rollout take?
No duration has been established for this rollout, and the time depends on content volume, number of permission models, identity integration and how much review the content needs before go-live. Ask any partner for a written schedule that breaks the work into discovery, installation, identity setup, migration trial, full migration, testing and handover, with the dependencies and client-side tasks called out. Ask what must be ready before the project starts, such as directory groups and a content owner list, since those are often the longest waits.
What does the work need from our own staff?
Plan for time from your identity team, a database or infrastructure owner, a content owner for each space, and someone who can approve permission design. Identity administrators map directory groups to wiki roles. Content owners decide what is current, what is archived and who can edit. Your security or compliance lead should review access rules and audit requirements. Ask a partner to list each role, the expected hours per role and when those people are needed, so your own calendar does not become the critical path.
When does a per-member SaaS workspace cost less?
A SaaS workspace can cost less when the user count is small, the content volume is modest and you do not have staff to run servers, patches and backups. Notion's pricing page, as read in October 2026, lists Plus at $10 and Business at $20 per member per month, and SAML SSO starts on the Business plan, with SCIM provisioning on Enterprise only. Multiply those rates by your headcount and years of use, then compare that total with hosting, migration and administration costs. Self-hosting tends to become more attractive as users grow, when data residency rules apply, or when identity and retention requirements need control you cannot configure in a vendor plan.
How do we get a fixed-scope quote?
Most DeployOpen engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts. DeployOpen does not publish a price list, and a quote follows from that written scope. To prepare, list your platform choice or open decision, number of users and spaces, content sources and volume, identity provider, hosting location, backup and retention needs, and required integrations. Ask the vendor to separate one-time work (installation, migration, hardening, training) from recurring work (support, upgrades, backups, testing), and to state what is excluded.
How records and audit needs add to the cost
Records and audit rules add cost to a self-hosted wiki mainly through configuration and evidence work, not licensing. SEC Rule 17a-4(b)(4) requires broker-dealers to preserve originals of communications received and copies of communications sent relating to the business, including inter-office communications, for not less than three years. The HIPAA Security Rule at 45 CFR 164.312 adds technical safeguards for ePHI, including access controls, audit controls under 164.312(b) that record and examine activity, and transmission security under 164.312(e)(1). A wiki holding procedures that touch these data sets will need audit logging turned on and retained, retention periods set for each space, role-based access reviewed on a schedule, and proof that those settings were applied and checked. Confirm which of your pages, comments and attachments count as regulated communications or ePHI before you scope the work, because that decision determines how much of the platform falls under these controls.
The wiki is often not the system of record for these rules. Communications under 17a-4 are usually held in an email archive or a dedicated compliance store, and clinical records stay in the EHR, so a wiki that merely links to or describes them may need far less retention machinery than one that holds the records themselves. Ask your counsel or external auditor to state in writing which systems carry the obligation, then price only those. Budget for the one-time work of mapping log sources to a retention store, testing that exports are complete, and writing the access review procedure, and for the recurring work of running those reviews and keeping evidence. Whether a self-hosted platform, a SaaS workspace or a partner-run deployment best fits the obligation is a decision to make only after that scope is settled.
How DeployOpen scopes and delivers a fixed-scope knowledge base
DeployOpen is a Chainscore Labs company that plans, implements, customizes, hardens, backs up and documents self-hosted open-source platforms inside the client's own infrastructure. For knowledge base cost, we start from a written scope that separates license, hosting, migration, support and administration costs so the build, partner or SaaS comparison rests on figures your team can verify.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- We list every cost line: software license, hosting, migration, integration, training and administration effort.
- We record which costs are one-time and which recur each year, so the quote can be compared against per-member SaaS pricing.
How we build
- We deploy the chosen wiki, such as BookStack, Outline or XWiki, in your cloud account, data center or isolated network.
- We configure identity integration, page permissions and migration of existing spaces, then test access for each reader group.
- We document hosting size, license terms and upgrade steps so the cost assumptions can be checked against the running system.
How we hand over
- We deliver runbooks, configuration records and an administrator guide that your team can use without us.
- We include a cost register showing license tiers, support contracts and hosting components with their owners.
- We confirm which vendor agreements, such as XWiki SAS support or consulting days, your organization holds directly.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, priced separately from the build.
- We track upstream release notes and license changes so that cost and compliance assumptions stay current.
- We review annual hosting, support and user-count changes with your team before renewal dates arrive.
