Document360 cost vs self-hosted BookStack: where the money goes
Most buyers arrive here with a renewal or quote that is hard to compare line by line. Document360 pricing is quote-based, and the figure you receive is shaped by team accounts, workspaces, languages, SSO and AI usage, so no fixed comparison can be stated without the written quote in hand. What you can do is list each of those drivers, confirm which ones your current contract prices separately, and ask the vendor to show how the total changes if you add a language, a workspace or a team. Those are the levers that move your cost, and they are the first things to put beside the self-hosted figures.
BookStack carries no license fee. It is released under the MIT license, and version v26.09.1 was published on September 29, 2026. That moves the cost to other places: the server or virtual machine that runs it, the MySQL 8.0 or MariaDB 10.6 or later database it requires, PHP 8.2 or later, backups and restore testing, staff time for setup, and the migration itself. Most of these costs are one-time for the build and recurring for hosting, patching, backups and administration. Ask whether your team will pay an internal platform group, an implementation partner or a mix, and whether the support plan offered by the BookStack project is worth buying. Each line item should be priced against the scope you agree in writing.
Your decision should rest on a side-by-side model that counts the same components on both sides: subscription or license, hosting, storage, backup, identity integration, migration, editor and admin hours, and ongoing upgrades. Label every assumption, including how many editors you have, how many languages you publish and whether customer-facing pages need authentication. Confirm with Document360 which AI and workflow features are bundled and which are metered, because those charges are the hardest to predict. Then price the self-hosted side against your own environment, and treat the difference as a decision input rather than a promised saving.
Which cost components change between the two options
This table sets each cost component of a Document360 subscription against the equivalent work for self-hosted BookStack, and marks whether each cost is one-time or recurring. Read it as a checklist for building a like-for-like comparison, since most of the Document360 side depends on your quote and most of the BookStack side depends on your own servers and staff time.
| Cost component | Document360 side | Self-hosted BookStack side | One-time or recurring |
|---|---|---|---|
| Subscription or license | Quote-based subscription, with price driven by team accounts, workspaces, languages, SSO and AI usage. Confirm which items are base and which are add-ons at renewal. | No license fee. BookStack is MIT licensed. Paid support plans and sponsorship are optional. | Document360: recurring. BookStack: none required, optional support recurring |
| Hosting and infrastructure | Vendor-hosted. Ask whether data residency, regional hosting or private network options carry an extra charge. | Your servers or cloud account running PHP 8.2 or later, plus MySQL 8.0 or MariaDB 10.6 or later. Sizing depends on users and attachments. | Recurring |
| Database | Included in the vendor service. Confirm backup retention and export options in writing. | Separate MySQL 8.0 or MariaDB 10.6 or later instance to provision, patch and monitor. Wiki.js 2.x recommends PostgreSQL 9.5 or later if that option is considered. | Setup one-time, operation recurring |
| Implementation and configuration | Vendor onboarding and set-up, often limited to the vendor's own feature set. Confirm what is included in the quote. | Installation on Ubuntu 26.04, 24.04 or 22.04 using official scripts, then SSO, roles and branding. Scope with a fixed written plan or internal staff. | One-time |
| Migration of existing content | Export from Document360 is possible, but the export covers what the vendor supports. Confirm attachments, comments and private notes are included. | Import and reformatting effort from the old source, plus validation of links, permissions and attachments. Effort depends on page count and format. | One-time |
| Backups and disaster recovery | Vendor-managed backup. Ask for recovery time and point-in-time options in the contract. | Your job: database and file backups, restore tests and off-site copies, handled by your team or a retainer partner. | Recurring |
| Upgrades and patching | Included in subscription. Changes arrive on the vendor's schedule. | Your team applies BookStack releases, PHP and database updates. Plan a test instance before each change. | Recurring |
| Internal skills and admin time | Smaller admin load for routine content and access work, though vendor-side configuration still needs an owner. | Editors need training on the WYSIWYG and Markdown editors. Admins need Linux, PHP and database skills for operations. | Recurring, with an initial learning period |
| Exit or export effort | Plan for export before the contract ends. Confirm what formats and scope the export returns. | Lower lock-in risk because content is stored in an open platform. Still plan a periodic export copy of the database and files. | One-time at exit, periodic copies recurring |
What moves the comparison up or down
Document360 is quoted against the scope you describe, so the biggest swings come from who edits, how many books and languages you run, and which sign-in rules you must meet. Each driver below maps to a cost component on both sides, so you can see which direction your own numbers will move.
Editors and reader population
Editor seats are the line most likely to be priced per person in a Document360 quote, so the count of authors, reviewers and admins drives that side directly. BookStack has no license fee per user, so the self-hosted cost grows mainly with server capacity for readers and with the admin hours spent managing accounts. Ask the vendor which roles count toward a seat, whether read-only viewers are free, and whether customer portal readers are billed separately from internal editors.
Number of books and shelves
Document360 quotes often change with the number of workspaces or projects you need to separate teams or audiences. In BookStack, books, chapters and shelves sit in one installation, so extra content adds storage and review effort rather than a new license line. Count the workspaces you truly need, because splitting content only for permissions is usually handled inside BookStack's role system. Confirm with the vendor whether each separate knowledge base is a billable unit.
Languages and translation work
Multilingual support is often a pricing tier on hosted knowledge bases, so each added language can move the quote. On the self-hosted side, the cost is translation labor, content duplication and the time editors spend keeping versions aligned, not a license. BookStack does not provide a translation workflow comparable to Document360's, so teams usually build a book per language or a naming convention. Estimate the number of languages and the update frequency before comparing quotes.
SSO and MFA requirements
If single sign-on or enforced multi-factor authentication sits in a higher pricing tier, the hosted quote rises with your identity requirements. BookStack supports OIDC, SAML2 and LDAP sign-in and multi-factor authentication that can be enforced per role, so the main self-hosted cost is configuring the identity provider and testing role mapping. Confirm which SSO protocols your identity provider uses and whether SCIM-style provisioning is required, since BookStack's account sync needs to be scoped in the implementation.
Attachments and data volume
Hosted platforms often bill or limit storage and attachments, and large image or PDF libraries can push a plan up. Self-hosting shifts this to disk, object storage and backup capacity that you size and pay for directly. Storage growth also raises backup duration and restore testing time, which is an operations cost that recurs each year. Measure your current attachment volume and growth rate, and ask the vendor what happens to content above plan limits.
Availability and in-house skills
Higher availability targets increase hosting cost on both sides. A self-hosted BookStack needs a PHP 8.2 or later stack with MySQL 8.0 or MariaDB 10.6 or later, plus backups, patching and monitoring that someone on your team owns. If your team already runs Linux, databases and containers, the ongoing work is modest, and if it does not, a fixed-scope implementation or retainer may be the larger line. Ask the vendor for the uptime commitment included in the subscription and compare it with the hours your team can staff.
How to build the model with your own numbers
This sequence turns a Document360 renewal and a BookStack deployment into a side-by-side model with your own quote, hours and content volume. The output is a three to five year comparison that separates one-time costs from recurring ones.
Collect the current Document360 quote and terms
Gather your current order form, renewal notice and any amendments, and list every line item the vendor charges for. Ask your account contact in writing for the renewal price, the term length, the notice period and the rules for adding seats, workspaces or languages mid-term. The step is done when you have a single document that shows what you pay today and what the next renewal would cost on the same terms.
List the features you pay for
Map each billed item to who uses it: team accounts, workspaces, translated languages, SSO, and any AI or workflow add-ons. Note which features are required for daily work and which were bought for a single project. Ask the vendor to confirm in writing which of these tiers gate SSO and AI usage, since pricing for those features is set by quote. The step is done when every billed feature has an owner and a business reason written beside it.
Size the self-hosted BookStack stack
Use BookStack's documented requirements to size the platform: PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later, plus a web server and storage for attachments. Decide between the official installation scripts for Ubuntu 22.04, 24.04 or 26.04 and a community Docker setup, since BookStack does not publish official Docker images. Your infrastructure team should price the virtual machines, database service, storage, and TLS certificates in your own environment. The step is done when you have a host specification and a monthly infrastructure line you can defend.
Estimate migration effort from content volume
Count pages, books, attachments and the total size of attachments, and identify which content has diagrams, embedded media or custom formatting. Export a sample from Document360 and test how it converts into BookStack pages before estimating. Your migration partner or internal team should record the hours per conversion and cleanup pass, then multiply by content groups. The step is done when you have a migration estimate tied to real samples and a list of content that will be rebuilt by hand.
Assign hours to editors and admins
Estimate how many hours per month editors spend writing and reviewing content, and how many hours admins spend on user management, backups, upgrades and permissions. Include the time to train staff on the BookStack editors, including the WYSIWYG and optional Markdown modes. Record who performs each task and whether the time is covered by existing staff or new hiring. The step is done when each role has a monthly hour estimate that you can multiply by an internal rate.
Request a written implementation quote
Ask an implementation partner for a fixed-scope written quote covering installation, SSO and MFA configuration, migration, backup setup, documentation and handover. DeployOpen works to written scope, deliverables and timelines agreed before work starts, and does not publish a price list, so the quote follows from the scope you define. Ask for the assumptions behind each line, what is excluded, and what ongoing support would cost as a separate retainer. The step is done when you hold a quote with listed exclusions and a clear split between one-time and recurring items.
Run the model over three to five years
Build a spreadsheet with one column per year across a three to five year horizon. Place one-time costs, such as migration, implementation and initial training, in the first year, and recurring costs, such as hosting, backups, support retainers, staff hours and renewals, in every year. Run the Document360 renewal scenario with the same assumptions, including expected price changes you have confirmed in writing. The step is done when both scenarios show annual totals and cumulative totals, and you can point to the source of every number.
Test the model against cost drivers
Change the inputs that move the result most, such as seat count, number of languages, content volume and the price of SSO or AI features, and see which assumption flips the outcome. Share the model with finance, IT operations and the content owners so each group can challenge its own inputs. Keep the sensitivity results with the decision record. The step is done when the team agrees which assumptions matter most and knows what to confirm before signing.
What migration costs and how export options affect it
Migration effort depends more on what you export and how much structure survives the move than on the tool you move to. Document360's export formats are covered in a sibling page, so this section focuses on the migration patterns that come up when teams arrive from other wikis, which is where most of the unplanned hours appear. Confluence and Notion both have documented export paths, but their behavior shapes the work differently. Notion's full workspace export can take up to 30 hours according to Notion, and its Include subpages option for PDF export is limited to Business and Enterprise plans. Enterprise workspaces can also disable exports entirely in security settings, so confirm your export rights before you plan anything. For Confluence, the XML site and space export reaches end of life on December 1, 2026, and Atlassian recommends CSV export after that date, so a move that depends on XML needs a timeline that finishes before then.
Migration time scales with several drivers: the number of pages, the volume and version history of attachments, how permissions map to the target's roles and spaces, and how many internal links must be rewritten to point at the new URLs. Each of these multiplies the others. A space with heavy embedded attachments and many cross-space links can take several times longer to clean up than a flat space of similar page count. Permissions deserve particular attention because group membership and page restrictions rarely map one to one onto BookStack's shelves, books and roles, so someone must decide which rules to keep and which to retire.
Before you budget, run a pilot on one representative space. Pick a space with typical attachments, a few restricted pages and internal links, export it, import it into a test BookStack instance, and log the hours spent on cleanup, link repair and permission review. Ask any implementation partner to quote against that measured effort and to state which items are excluded, such as attachment history, comments or content the source export leaves out. Confirm the export limits and deadlines directly with the source vendor, since they can change, and use the results to set a realistic cutover window.
BookStack or Wiki.js: which fits which cost profile
BookStack suits a team that wants content organized as books, chapters and pages grouped on shelves, with a WYSIWYG editor, an optional Markdown editor and built-in diagrams.net diagrams. Its sign-in options cover OIDC, SAML2 and LDAP, and it ships with multi-factor authentication that administrators can enforce per role, so the identity work often stays within one platform. Costs are mostly the server, the database and the admin time to keep both current. Cost components to plan for:
- Software license: BookStack is MIT licensed, so there is no license fee to pay for the wiki itself.
- Runtime: It requires PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later, which your team must patch and support.
- Installation path: Official installation scripts exist for Ubuntu 26.04, 24.04 and 22.04. BookStack does not publish official Docker images and points to community setups such as LinuxServer.io, which your security team should review before adoption.
- Role model: Per-role MFA and the permission system reduce the number of separate tools that need configuration.
- Support: Paid support plans are available from the project, which adds a recurring cost only if you choose them.
Confirm with your identity team that your IdP speaks OIDC, SAML2 or LDAP, and decide in advance whether you will run a community Docker image or the scripted install.
Wiki.js suits a team that needs its content to sync with a Git repository or an S3-style store, or that wants a wider list of sign-in modules. Its storage modules include Git, AWS S3 and DigitalOcean Spaces, and some modules such as Git synchronize content in both directions. That bidirectional sync can reduce the effort of keeping documentation in a repository, but it adds configuration, testing and a dependency on the storage path. Cost components to plan for:
- Authentication breadth: Modules include Azure AD, GitHub, Google, Keycloak OpenID Connect, LDAP and Active Directory, generic OpenID and OAuth2, Okta and SAML 2.0, with TOTP two-factor authentication.
- Hosting constraints: Wiki.js requires a dedicated domain or subdomain, cannot be mapped to a subfolder, and needs at least 1 GB of RAM on Linux.
- Database: The 2.x line recommends PostgreSQL 9.5 or later and also supports MySQL, MariaDB, MS SQL and SQLite. The PostgreSQL search module needs the pg_trgm extension.
- Maturity: The main requarks/wiki repository holds Wiki.js 3.0, which is marked beta and not for production use. Plan the deployment around the 2.x line, with v2.5.316 as the latest release the source supplies.
- Sideloading: It supports sideloaded files for environments without internet access.
Confirm which storage module your Git or S3 workflow needs, and test the sync direction with a copy of real content before you commit.
The two platforms place their cost in different spots. BookStack's footprint is a PHP application with a relational database, and its admin work centers on the server stack and the role model. Wiki.js needs a dedicated hostname and a minimum memory allocation, and its maturity depends on pinning the 2.x line while the 3.0 beta is not production-ready. Those differences change who you need on the project and how long the setup takes. Items to weigh:
- Infrastructure: Both run on your own servers, so hosting, backups and patching recur regardless of the choice.
- Operating skills: A PHP and MySQL or MariaDB stack suits teams already running that stack. A Node.js application with a PostgreSQL search module suits teams already running Node and PostgreSQL.
- Version pinning: For Wiki.js, budget time to track the 2.x releases and avoid the beta line. For BookStack, track the monthly style releases, such as v26.09.1 published on September 29, 2026.
- Editor time: Consider how often editors need Markdown versus WYSIWYG, since BookStack offers both and Wiki.js editor choices affect training.
- Quote scope: Ask any implementation partner to price installation, identity integration, storage sync testing and backups as separate line items.
Illustrative example: a team with an existing Keycloak and a Git-based docs workflow may find Wiki.js fits better, while a team that mainly needs per-role MFA and LDAP sign-in may find BookStack fits better.
Questions buyers ask before comparing cost
How much effort does self-hosting BookStack take, and who does the work?
The effort depends on content volume, the number of integrations and how much of the setup your team already has in place. BookStack is MIT licensed and runs on PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later, and it ships official installation scripts for Ubuntu 26.04, 24.04 and 22.04. Your platform or systems team installs and maintains the server, your identity team connects single sign-on through OIDC, SAML2 or LDAP, and your content owners rebuild shelves, books and permissions. Ask an implementation partner to scope each of these pieces in writing before you compare any figure against a Document360 quote.
How long does a migration from Document360 to BookStack take?
No fixed duration applies to every migration, because the timeline is driven by how many articles you have, how many languages they cover, how many attachments and images must move, and how much restructuring you want during the move. Document360 offers an offline HTML site and ZIP and JSON project exports, so the export format and its gaps set the first step. Plan for a pilot space, a content mapping exercise and a permission check before a full cutover. Your partner should confirm the schedule against your content inventory in the written scope.
Can our internal team run BookStack without outside help?
Many teams can operate BookStack in-house once a platform engineer has deployed it, because the application is a standard PHP and MySQL or MariaDB stack with a published installation guide. The harder parts are the ones outside the wiki itself: backups of the database and uploaded files, upgrades between releases such as v26.09 and v26.09.1, security patching of the operating system and the web stack, and monitoring. Confirm internally who owns each of these tasks. If nobody does, a retainer for upgrades and support is a cost to include in your comparison.
What recurring costs remain after a self-hosted BookStack launch?
The license fee is zero, so recurring costs come from the components you run and the people who maintain them. These include the server or cloud instances, database hosting, storage and backup capacity, outbound email for notifications and password resets, and staff time for upgrades, patching and access reviews. If you choose paid support, BookStack's maker offers paid support plans, which is a separate line item you can include or leave out. Ask each cost to be listed by component so you can compare it with the recurring line items in a Document360 quote.
Does the cost change if our team or content library grows?
Self-hosted BookStack has no per-seat or per-workspace license fee, so growth changes your infrastructure and administration load rather than a vendor invoice. Storage for attachments, database size, backup volume and search indexing grow with content, and more editors add review and support work. Document360 pricing is quote-based and driven by team accounts, workspaces, languages, SSO and AI usage, so ask the vendor to show how each of those drivers changes the total at your projected size. Model both scenarios with your own numbers rather than relying on a general rule.
Which SSO and security features do we get with BookStack?
BookStack supports OIDC, SAML2 and LDAP sign-in, built-in multi-factor authentication that can be enforced per role, and a full role and permission system. Confirm these against your identity provider and your access policy before assuming they match your current setup. Whether SSO adds a charge depends on the vendor, so compare that line directly, and include the effort to configure and test each sign-in path in your own estimate.
What should we ask for in a Document360 quote and a BookStack implementation scope?
Ask the Document360 vendor for a written quote that lists each driver separately: team accounts, workspaces, languages, SSO and AI usage, along with renewal terms and what happens when counts increase. For a self-hosted option, ask an implementation partner for a fixed-scope proposal that states deliverables, timelines and responsibilities in writing. Include hosting, backup and restore testing, migration of content and attachments, permission mapping, sign-in configuration, documentation and handover. DeployOpen plans, implements, integrates, hardens, backs up, upgrades and documents self-hosted platforms in your own infrastructure, and provides scoped quotes from a written scope. It does not publish a price list.
Is BookStack the right fit, or should we compare Wiki.js or XWiki first?
BookStack suits teams that want a book, chapter and page structure with a WYSIWYG editor, an optional Markdown editor and built-in diagrams.net diagrams. Wiki.js suits teams that want storage modules such as Git, which can synchronize content in both directions, and it requires a dedicated domain or subdomain. XWiki suits larger documentation teams that need structured applications and extensions. Compare the cost of each option only after you have confirmed how your content is organized and who will maintain it.
When self-hosting costs less and when it does not
Self-hosting usually removes the recurring license line, but it moves the cost into staff time and infrastructure that someone must own every month. With BookStack, the MIT license carries no fee, so the recurring spend shifts to the server or cloud account that runs PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later, the backup storage, the editors' and admins' hours, and whatever support plan the organization chooses. Document360 is priced by quote, and that quote is shaped by team accounts, workspaces, languages, SSO and AI usage. Those drivers grow with headcount and with the number of audiences, so the gap between the two models tends to widen as the wiki spreads across more teams. Ask Document360 for a written quote that shows each of those drivers separately, so you can see which one moves the price.
The model favors self-hosting when the organization already runs web applications, databases and backups with platform skills, when data residency or sovereignty rules keep documentation inside its own environment, or when the user population is large enough that per-seat pricing grows faster than the fixed cost of the servers. It can cost more for a small team without operations staff, because a single administrator patching PHP, the database and the backup job can absorb more hours than the license would have cost. Interpret the outcome with care: a wiki that is rarely updated or upgraded may look cheap on paper and then become expensive when a security patch arrives during a busy quarter.
Before you compare totals, confirm the inputs with Document360 and with any implementation partner you are considering. Ask Document360 for the exact components and renewal terms in your quote, and ask the partner for a fixed-scope estimate covering installation, SSO and multi-factor setup, content migration, backup testing and upgrade procedures, with the staff hours each one assumes. Then build a three-year comparison that separates one-time work from recurring work, and test it against your own user counts and language needs rather than against an illustrative example.
How DeployOpen scopes a fixed-price implementation
DeployOpen plans and implements self-hosted open-source platforms inside your own infrastructure, so the cost of moving from Document360 to BookStack becomes a written scope you can review. We start from your actual licensed seats, workspaces, languages and integrations, then agree deliverables before any work begins.
How we scope
- We inventory Document360 team accounts, workspaces, languages, SSO use and AI features that your current contract covers.
- We agree a written scope for BookStack hosting, database, backups, SSO and content migration before work starts.
- Engagements are fixed-scope, and we confirm what is in and out, including editor and admin training, in writing first.
How we build
- We install BookStack in your cloud account or data center, with PHP 8.2 or later and MySQL 8.0 or MariaDB 10.6 or later.
- We configure OIDC or SAML2 sign-in, enforced multi-factor authentication by role, and permissions that mirror your access model.
- We test a sample migration of books, chapters and pages from your Document360 export, then document the field mapping and gaps.
How we hand over
- You receive architecture notes, runbooks for backup and restore, and an admin guide written for your environment.
- We walk your editors and admins through the page structure, the editor options and the permission model that you will own.
- We record the decommissioning steps for Document360 so your team knows which exports to keep before the contract ends.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover, scoped separately in writing.
- Upgrades to new BookStack releases are planned and tested in a staging copy before they reach production users.
- Ask any implementation partner to confirm response times, ownership of backups and who holds the admin credentials in writing.
