Slite cost vs self-hosted Docmost: where the money actually goes
Self-hosted Docmost removes the per-user Slite subscription, but it replaces that line with hosting, database, backup and staff time, so the outcome depends on headcount and on which features you need. Before comparing totals, check Slite's current prices on its pricing page, because this section does not state them. Docmost's Community edition is free to self-host, which makes the software licence the smallest cost in the model. The Business plan is priced at $6 per seat per month billed annually with a 10-seat minimum. As an illustrative calculation, ten seats on Business come to $720 a year before any infrastructure cost. Confirm the current terms on Docmost's pricing page.
The recurring costs of self-hosting sit in separate components, and each is paid to a different party. Your cloud or data centre bill covers the Docmost application, a PostgreSQL 18 database and a Redis 8 instance, as the reference Docker template runs them. Files are stored locally by default, so you must size disks or budget for S3-compatible or Azure Blob storage. Database and attachment backups need their own schedule and restore tests. Staff time covers installation, an APP_SECRET of at least 32 characters, WebSocket support on the reverse proxy, upgrades and out-of-hours response. Staff time is usually the largest unknown, so ask for a written estimate that splits one-time setup and hardening from recurring upkeep.
Identity requirements can change the answer more than seat count. Docmost's documentation places SAML 2.0 or OIDC single sign-on, LDAP and SCIM provisioning in its paid editions, and the Enterprise tier adds audit logs and SIEM integration. Community may therefore not cover centralized sign-on or joiner and leaver provisioning, and the cost of the required edition should enter the model from the start. Confirm which Docmost edition carries each control your policy requires, and ask Slite which of its plans includes SSO and SCIM for your seat count. Put both answers in writing before you compare totals.
Which cost components change when you self-host Docmost
This table lists each cost component of moving from Slite to self-hosted Docmost or BookStack, who is paid for it, and whether it is one-time or recurring. Slite's per-user prices are not in the sources used here, so confirm them with Slite for your seat count and plan tier. The main takeaway is that Docmost Community and BookStack remove the license fee, but hosting, database operations and staff time remain recurring costs.
| Cost component | Who is paid | One-time or recurring | What drives it |
|---|---|---|---|
| Slite subscription | Slite, per user | Recurring | Seat count and plan tier. SSO sits on Pro and SCIM on Enterprise; confirm current pricing with Slite. |
| Docmost Community licence | No license fee (AGPL-3.0 core) | Recurring costs only for hosting and operations | Free self-hosted edition, but it omits paid features such as SAML or OIDC SSO, SCIM and the Confluence importer. |
| Docmost Business licence | Docmost, per seat | Recurring | Listed at $6 per seat per month billed annually with a 10-seat minimum (Docmost pricing page). Confirm the current rate before budgeting. |
| BookStack licence | No license fee (MIT); optional paid support to BookStack | Recurring only if you buy support | Support plans are optional. Ask BookStack whether a support plan fits your environment. |
| Hosting compute and network | Your cloud provider or data center | Recurring | Concurrent users, number of environments and availability targets. Size with your own load test. |
| PostgreSQL 18 and Redis 8 | Cloud provider for managed services, or your database team | Recurring | Docmost's compose template uses these images. BookStack instead needs MySQL 8.0 or MariaDB 10.6 or later. |
| File storage | Your storage provider | Recurring | Docmost stores files locally by default; S3-compatible or Azure Blob storage are options. Attachment volume drives growth. |
| Backups and restore testing | Your operations team, or a partner if contracted | Setup one-time; testing and retention recurring | Database and attachments must be backed up together and restored in a test environment. |
| Migration from Slite | Your team or an implementation partner | One-time | Export scope, page tree rebuild, permission re-creation and embed checks. Agree scope in writing. |
| Upgrades and internal skills | Internal staff, or a retainer provider | Recurring | Release cadence, such as Docmost v0.96.0 published September 8, 2026. Plan time for testing each upgrade. |
What moves the Slite versus Docmost comparison
Five or six decisions set most of the difference between a Slite subscription and a self-hosted Docmost deployment. Seat count, the features that sit in Docmost's paid edition, storage, availability and team skills each change the total cost in a different way, so check them together before comparing invoices.
Seat count against the minimum
Docmost's Business plan is priced per seat per month billed annually, with a 10-seat minimum. Teams below that threshold pay for seats they do not use, while larger teams should compare the per-seat Business price with Slite's per-user plans at the same headcount. Count active editors and readers separately, because read-only viewers may change the math. Ask Docmost for current terms before you model the numbers.
Features behind the paid edition
Several features that teams expect from a wiki sit in Docmost's paid editions: SSO with SAML 2.0 or OIDC, SCIM provisioning, page-level permissions, and the Confluence, DOCX and PDF importers. Confirm which of these your identity provider and migration plan require before assuming the Community edition covers you. SAML and OIDC sign-in are the first items to verify against your directory.
Attachment volume and storage choice
Docmost stores files on local disk by default, with S3-compatible or Azure Blob storage as options. Attachment volume drives the storage line, the backup size and the restore time. Estimate how much of your current content is images, videos and PDFs, and choose object storage early if the volume is large. Ask Slite how attachments are exported so you know what must be copied.
Availability requirements
A single Docker host with local file storage is simpler to run than a highly available setup, but it has one failure point. Decide how long the wiki can be unavailable, who is on call, and whether you need a standby database. Real-time editing relies on WebSockets, so the reverse proxy and any load balancer must pass them through. These choices add infrastructure and staff time that a hosted plan does not charge you for directly.
Existing container and database skills
Docmost's recommended installation runs on Docker with PostgreSQL 18 and Redis 8 images, and requires an APP_SECRET of at least 32 characters. If your team already operates Docker, PostgreSQL and Redis, the run cost is mostly routine upkeep. If it does not, budget for training or outside support, which is a one-time cost, and for ongoing patching, which recurs. Kubernetes adds another layer to maintain, so confirm whether you truly need it.
How to build the Slite cost model with your own numbers
This sequence turns a vague sense that Slite costs too much into a side-by-side model built from your own seat count, plan terms, hosting prices and staff time, so the comparison holds up in a renewal or budget discussion.
Pull your current Slite seat count and plan
Start from your latest Slite invoice or billing portal. Record the number of paid seats, the billing interval, the plan tier you are on, and any add-ons. Note which features that tier includes, especially whether SSO sits on the tier you pay for and whether SCIM provisioning is included. Ask your Slite account contact to confirm current per-seat pricing and any discount terms in writing. The step is done when you have one line per cost item with its source document attached.
List the features your team depends on
Ask the wiki owners, security lead and admins to name the features they would miss on day one. Typical items include real-time editing, spaces and page permissions, search, diagrams and embeds, page history, SSO, multi-factor authentication, provisioning, audit logs and any AI features. Mark each as required, nice to have or unused. Compare the list against the Docmost documentation so you know which items sit in the paid edition. The output is a feature inventory that drives the edition choice in the next step.
Choose the Docmost edition that matches the inventory
Map the required features to Docmost's editions. The Community edition is free to self-host, but the documentation lists SSO with SAML or OIDC, LDAP, SCIM provisioning, MFA, page-level permissions, the REST API, and the Confluence, DOCX and PDF importers as paid-edition features. Business is priced per seat per month with a 10-seat minimum on Docmost's pricing page, and Enterprise is quoted individually. If you need SCIM or audit logs, Enterprise is the relevant line. Confirm the license terms for code under the Enterprise license with Docmost before you commit. The output is a single named edition per scenario.
Price hosting, database and storage in your cloud
Price the infrastructure you would run yourself, using your own cloud or data center rates. Include the application server, PostgreSQL and Redis (the compose template uses PostgreSQL 18 and Redis 8 images), file storage, which is local by default with S3-compatible or Azure Blob options, a reverse proxy that supports WebSockets, TLS certificates, monitoring and the backup target. Ask your infrastructure team to size environments for production and a separate test instance. The output is a monthly and annual infrastructure line with the rate source noted for each item.
Estimate migration and staff hours per component
Break the one-time work into components: exporting Slite content as Markdown or HTML, preparing ZIP archives, rebuilding the page tree and internal links, re-creating permissions, checking embeds and images, and setting up SSO. Estimate hours for each component using your own team's rates, or ask a partner for a fixed-scope quote based on the same list. Add recurring staff time for upgrades, backups, restores and user administration. Note that the Slite export format and the page count drive most of this effort, so take a sample export early. The output is a one-time effort table and a recurring operations table.
Request current prices from each vendor
Before you finalize the model, ask Slite for a current quote on the seat count and tier you need, and ask Docmost for current Business or Enterprise pricing for the same seat count. Pricing changes, so do not rely on numbers copied from older pages or from this comparison. Ask each vendor to state what is included, billing intervals, minimum seats, renewal increase terms and data export options. Record the quote date and reference on your model. The output is two vendor quotes you can cite in the model.
Compare totals over a fixed horizon
Choose one horizon for every scenario, such as the length of your next contract term, and place Slite subscription costs beside Docmost license, infrastructure, migration and staff costs for that period. Separate one-time costs from recurring ones so the first-year figure is not confused with steady-state spend. Run a sensitivity check by changing seat count and hosting rates, since seat growth drives the Slite line and fixed infrastructure drives the self-hosted line. The model is complete when each scenario shows a total cost, the assumptions behind it, and the sources for every number.
How Docmost, PostgreSQL, Redis and storage fit together
The self-hosted Docmost stack has four moving parts, and each one creates its own cost line. The Docmost application runs in a container, while the Docker compose template used for installation runs PostgreSQL 18 and Redis 8 images alongside it. Your team pays for the compute to run all three, for the storage behind the PostgreSQL database and attachments, and for the time to patch, back up and restore each component. Before you approve a budget, confirm with Docmost's installation documentation which versions the current compose file pins, because those images are what your operations team will maintain.
File storage is the decision with the most effect on long-term cost. Docmost stores files on local disk by default, which costs nothing extra in licensing but makes you responsible for disk capacity, snapshots and off-site copies. The S3-compatible and Azure Blob options move attachments to object storage, which shifts cost to a storage bill that recurs with volume. Ask your platform team which option fits your backup design, and price the database and file backups together, since restoring a wiki requires both the PostgreSQL data and the matching attachments. Also confirm that APP_SECRET is set to at least 32 characters before first start, because it is a configuration value you cannot treat as optional.
The reverse proxy is the component most often underestimated in the estimate. Real-time editing depends on WebSockets, so the proxy in front of Docmost must allow them, and any load balancer or CDN layer you add in the path must pass them through without timing out idle connections. Someone on your team owns that configuration, tests editing from two browsers, and keeps it correct through certificate and proxy upgrades. That work is a one-time setup cost followed by a recurring operations task, and it is the item to name explicitly when you request a quote for an implementation scope.
What the Slite to Docmost migration costs in effort
The one-time cost of moving from Slite to Docmost is mostly labor, and it is driven by how much content and structure you carry across. The work covers exporting Slite content as Markdown or HTML, importing the archives into Docmost spaces, rebuilding the page tree and internal links, re-creating permissions for spaces and groups, and checking embedded media and images after the move. Each of those steps has a person attached to it, whether that is your own administrator, an internal project lead or a services partner working to a written scope.
Effort depends on three variables: page count, link density and permission complexity. A small workspace with flat pages and open access can move quickly, while a deep page tree with many cross-links to Slite pages, and spaces with restricted reader and editor roles, takes longer to verify. Docmost's import dialog accepts Markdown and HTML files, including in a ZIP archive, Word DOCX documents, a Notion export ZIP and a Confluence export, and pages or whole spaces export as Markdown or HTML. The DOCX importer is a paid-edition feature, so if your Slite content is mainly Word files, confirm which edition you need before you plan the import route.
Measure the effort on a pilot space before committing to a full move. Pick one representative space with typical link density, embeds and permission rules, run the export and import end to end, and time each step, including the manual fixes to internal links and image paths. Use those measurements to ask any services provider for a fixed-scope quote, and confirm with Docmost's documentation which edition covers the features your pilot depends on. Recurring costs, such as hosting, database maintenance and Docmost seat licenses, continue after the migration and should be budgeted separately from this one-time effort.
Slite cost vs self-hosted Docmost questions buyers ask
Is self-hosting Docmost cheaper than Slite overall?
It depends on the number of seats, the edition you need and how much of the running cost your own staff already carry. Docmost's Community edition is free to self-host, so the license line disappears, but you still pay for servers, storage, backups, PostgreSQL and Redis, and the time to install, configure and patch them. Slite is priced per user, so its total grows with headcount. Ask Slite for the plan that includes the features you need, then build a three-year model for each option that lists hosting, staff time, backup storage and any paid Docmost seats. Compare the totals, not the license lines alone.
What drives the effort and time to move off Slite?
The main drivers are the volume and structure of your content, how many people need access rules, and how many embeds, images and internal links must survive the move. Docmost's docs describe importing Markdown and HTML, including ZIP archives, and exporting pages or whole spaces as Markdown or HTML, so the export format and the state of your Slite workspace will shape the work. Permissions are usually re-created by hand, and embeds and images need checking after import. Ask any implementation partner for a written scope that lists the spaces, the number of pages and the permission model before work starts.
What does a self-hosted wiki need from our own staff?
Your staff must own the hosting environment, which means container hosting, a reverse proxy with WebSockets enabled for the real-time editor, TLS certificates, backups and restore tests, and upgrades. Docmost's installation guide describes a Docker-based setup with PostgreSQL 18 and Redis 8 images, an APP_SECRET of at least 32 characters, and local file storage by default with S3-compatible or Azure Blob storage as options. Someone must also manage user accounts through SSO and handle support requests. Estimate the hours per month for these tasks with your platform team before choosing a path.
Can our team deploy Docmost without outside help?
A team with container and database experience can usually deploy Docmost from its published compose template, but the harder work is production readiness: secrets handling, backup and restore testing, network controls, monitoring and a tested upgrade path. Whether your team can do this alone depends on its current skills and on-call capacity. Many organizations split the work, keeping routine operations in house and buying a fixed-scope engagement for design, hardening and migration. DeployOpen plans, implements, hardens, backs up, upgrades and documents self-hosted platforms in your own infrastructure, and most engagements are fixed-scope with the scope agreed in writing before work starts.
Which Docmost edition do we need for SSO and SCIM?
SSO through SAML 2.0 or OIDC, LDAP, SCIM provisioning and multi-factor authentication are listed as paid-edition features in Docmost's documentation. Docmost's pricing page lists a free self-hosted Community edition, a Business plan at $6 per seat per month billed annually with a 10-seat minimum, and an Enterprise plan at custom pricing that adds SCIM, audit logs and SIEM integration. Note that Docmost's core is AGPL-3.0, while the ee directories fall under the Docmost Enterprise license. Confirm the exact feature split with Docmost before you commit, because editions can change.
Does BookStack's no-license-fee model change the math?
Yes, it removes the per-seat license line entirely, because BookStack is MIT licensed and does not publish a paid tier. Your cost then shifts to hosting, MySQL or MariaDB, staff time and any support plan you buy from the BookStack project. BookStack requires PHP 8.2 or later and MySQL 8.0 or MariaDB 10.6 or later, and it lacks official Docker images, so you will rely on community images or official installation scripts. Compare BookStack's operating cost with Docmost's, including any SSO or SCIM features you need, which Docmost keeps in its paid edition.
What should we ask for in a quote for this migration?
Ask for a written scope that lists the workspaces, spaces and approximate page count, the export method, the target hosting model, the backup and restore approach, and the SSO and permission model to be rebuilt. Request the deliverables and acceptance checks, such as embed and image verification and a permission review, plus the post-launch support period and any retainer for upgrades. Ask how the quote handles one-time work separately from recurring operations. Confirm whether the quote covers Slite export help, the Docmost license choice and staff training, so you can compare offers on the same basis.
When staying on Slite is the better business case
Staying on Slite is the stronger choice when the hosted subscription costs less than the time your team would spend running a wiki. That is most likely for a small team with a handful of seats, no data residency rule that keeps documentation inside your own network, and no platform engineers who can take on patching, backups and upgrades. In that situation, a per-user price is easy to budget, and the vendor carries the work of uptime and maintenance. Before deciding, ask Slite for the current plan terms, the seat count at which pricing changes, and which features (SSO, SCIM, permissions, export options) sit on which tier, because these details change and this page does not set them.
The self-hosted route carries costs that a subscription hides. Docmost's Community edition has no license fee, but you pay for the server, the PostgreSQL and Redis services, storage, backups, monitoring, TLS and the staff hours to run them. If Docmost's paid edition is needed for SSO with SAML or OIDC, SCIM or page-level permissions, you also pay its per-seat rate, which has a 10-seat minimum on the Business plan. For a very small team, those recurring and staff costs can exceed the Slite bill. Ask your team to total the hours needed for a monthly patch cycle, a tested restore and a Docmost version upgrade, then compare that figure with the seat price before you commit.
Vendor-managed uptime is the other part of the case. A hosted service removes the question of who answers when the editor stops syncing at 2 a.m., and it removes the need to keep Docmost's real-time editing WebSocket path working through your reverse proxy. Staying on Slite also avoids a migration project for now. If your situation changes later, such as a compliance requirement or a seat count that grows past the point where the subscription stops being cheap, the export and migration path stays available. Plan a review date rather than treating the current choice as permanent.
How DeployOpen scopes a fixed-price Docmost implementation
DeployOpen is a Chainscore Labs company that plans, implements, hardens, backs up and documents self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a Slite to Docmost move, we agree the scope, deliverables and timeline in writing before work starts, so the cost of ownership you compare is the one you actually sign for.
How we scope
- We inventory Slite workspaces, channels, docs, permissions and integrations before estimating any work.
- We confirm which Docmost edition you need, since SSO, SCIM and page verification sit in paid editions.
- We write the hosting target, PostgreSQL and Redis layout, and backup approach into the scope document.
How we build
- We deploy Docmost with Docker in your environment, using the PostgreSQL and Redis images named in the installation guide.
- We configure the APP_SECRET, file storage (local, S3-compatible or Azure Blob) and WebSocket support on your reverse proxy.
- We test imports of Markdown, HTML and Notion or Confluence exports, then check embeds, images and internal links.
How we hand over
- We document the deployment, configuration keys, backup and restore steps, and the permission model as delivered.
- We run a restore test from backup and record the result so your team can repeat it.
- We walk your administrators through user provisioning, space permissions and day-to-day operations before handover.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Upgrades to new Docmost releases are scoped and tested in a staging copy before they reach production.
- Ask any provider, including us, to put support response expectations and upgrade responsibilities in writing.
