What does intranet software cost when you self-host it?
The intranet software cost of a self-hosted platform is rarely the licence. HumHub, XWiki and Nextcloud can be downloaded and run without a licence fee for their community editions, so the money sits in hosting, vendor subscriptions, onboarding and theming, content migration and the moderation effort that keeps spaces current. The total depends on three things: how many people will log in, how deeply the intranet is tied to your directory and single sign-on, and how much vendor support you need when something breaks. For a CIO or HR lead comparing this with a per-user SaaS intranet, those three variables matter more than the headline price of either option.
Split the costs into one-time and recurring lines before comparing. One-time work includes installation, directory and SSO integration, theming, and migrating existing pages or files. Recurring lines include infrastructure, backups, patching, vendor subscriptions and the internal time spent moderating content. Subscriptions scale with headcount in different ways. XWiki's Pro and support tiers are sized by user band, from Starter (up to 25 users, cloud only) to Enterprise (unlimited users), and XWiki pricing states that cloud and on-premises pricing is the same. Nextcloud Enterprise is priced per user per year with a 100-user minimum. Moving from Confluence has its own line: XWiki SAS lists Confluence Migrator Pro from 2000 EUR. Confirm with HumHub whether the edition you need covers directory and news features, because that is a licensing question, not a hosting one.
DeployOpen does not publish a price list. A quote follows from written scope, and most engagements are fixed-scope, so the scope document is where the intranet software cost is actually decided. Ask any implementation partner to price these items separately: infrastructure sized for your user count, identity integration, theming and page templates, content migration with a defined number of pages and attachments, moderator training, the upgrade cadence and the support tier. For each line, ask whether it is one-time or recurring and what drives it up. Then compare the total with a per-user SaaS subscription over the same period, including the internal effort your team would still carry. A quote that does not show these lines separately cannot be compared with a SaaS proposal.
Which cost components sit in-house, with a partner, or in SaaS?
This table compares who pays for each intranet cost component when you build in-house, buy a partner engagement, or subscribe to a per-user SaaS intranet, and whether each cost is one-time or recurring. Read the rows as a checklist for a quote: most of the recurring cost sits in administration, upgrades and moderation, not in the licence. The main takeaway is that the software line is often the smallest item once hosting, identity and ongoing staffing are counted.
| Cost component | Who is paid or who pays | One-time or recurring | What drives it |
|---|---|---|---|
| Hosting and infrastructure | In-house: your cloud or data center team. Partner: often billed through your own cloud account. SaaS: included in the per-user fee. | Recurring | User count, storage, backup retention and whether you need high availability or a separate test environment. |
| Software licence or subscription | Open-source core is free to download. Vendor support subscriptions go to the vendor, for example XWiki Pro tiers or Nextcloud Enterprise. SaaS: vendor per-user fee. | Recurring if you buy support or SaaS; none for the community core | Edition needed for directory login or advanced modules, and the user tier you fall into. |
| Nextcloud Enterprise list price (example) | Paid to Nextcloud GmbH per user per year, with a 100-user minimum (Nextcloud pricing page). | Recurring, annual | Tier chosen (Standard, Premium or Ultimate) and user count. List starts at 71.29 euros per user per year for Standard at 100 or more users. |
| XWiki Pro and support tiers (example) | Paid to XWiki SAS. Starter, Basic, Business and Enterprise tiers are sized by user count (XWiki pricing page). | Recurring, annual | Number of users and whether you need on-premises support, since cloud and on-premises pricing are stated as the same. |
| Installation and configuration | In-house staff time, a partner under a written scope, or XWiki SAS installation help if you hold a suitable plan. | One-time | Number of integrations, custom apps, and whether the platform runs in a restricted network. |
| Identity integration (LDAP, SSO) | In-house identity team or a partner. Some SSO connectors are edition-gated, so the vendor may charge a subscription. | One-time build, then recurring maintenance | Directory structure, number of identity sources and whether SAML or OpenID Connect is required. Confirm the edition with the vendor. |
| Theming and branding | Internal designers, a partner or a SaaS vendor's included options. | One-time, with periodic updates after upgrades | Depth of custom templates, number of audiences and how often the theme must be retested after upgrades. |
| Content migration | Partner or internal team. XWiki SAS sells Confluence Migrator Pro from 2000 EUR, and its trial is limited to 30 pages per migration (XWiki Store). | One-time | Volume of pages and attachments, permissions mapping and whether attachment history must be kept, since that tool keeps page history but not attachment history. |
| Training and onboarding | Vendor training is sold per day (for example, XWiki SAS lists training at 1500 EUR per day). Internal change teams or a partner otherwise. | One-time for initial training, recurring for new joiners | Number of audiences, mobile access needs and whether managers need separate sessions. |
| Ongoing administration and upgrades | In-house administrators or a retained partner. Nextcloud documents one-major-version-at-a-time upgrades with a backup before each. | Recurring | Release cadence of the chosen platform, number of third-party apps that need compatibility checks and staff availability for testing. |
| Moderation and content governance | Internal communications or community managers. This is staff time, not a licence line. | Recurring | Volume of posts, number of spaces and whether mandatory notices or approvals are required. |
| Per-user SaaS fees | Paid to the SaaS vendor for every licensed user, usually monthly or annually. | Recurring, scales with headcount | Number of users, add-on modules and contract term. Ask for the full per-user price, including minimums. |
How the three options differ for a mid-sized employer
Your own staff install, configure, theme, integrate and operate HumHub, XWiki or Nextcloud. No vendor is paid for delivery, so the cost sits in internal salaries and the time they spend away from other work. The open-source licenses carry no license fee for the community editions, but the features you need may sit in paid editions, so confirm that before you commit. Control stays entirely with you: data location, upgrade timing, and the choice of modules and integrations all remain in your hands.
- Staff time: Platform engineers, a content owner and an administrator must be staffed for setup and for the life of the intranet, not only for launch.
- Upgrade work: Nextcloud requires upgrading one major version at a time with a backup before each step, which becomes a recurring internal task.
- Feature gaps: Directory integration, SAML or OpenID Connect, and specific connectors may require paid editions or custom development that your team must maintain.
- Support path: Without a support contract, fixes depend on community channels and internal expertise, which can slow incident response.
- Typical risk: Key-person dependency. When the one engineer who understands the theming and directory mapping leaves, the intranet becomes fragile.
Before choosing this route, ask internally who will own each recurring task and whether that capacity is funded for several years.
An implementation partner plans, deploys, integrates and documents the intranet inside your own infrastructure, then hands over or supports it under agreed terms. DeployOpen works this way for self-hosted open-source platforms, and most engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts. You pay for the delivery project and then choose whether to keep ongoing support, upgrades and testing on a retainer or to run the platform internally.
- One-time delivery: Scoping, installation, directory and SSO integration, theming, content migration and training are priced against the written scope.
- Recurring vendor costs: XWiki Pro and support subscriptions and Nextcloud Enterprise are priced by user tier, so the subscription cost is tied to the size of your user base rather than to every individual change.
- Recurring service costs: Retainers for upgrades, patching and monitoring are optional but common, and should be quoted separately from the project.
- Control: Hosting, data location and configuration remain in your infrastructure, while the partner's obligations are defined in the statement of work.
- Typical risk: Scope drift and handover gaps. Unclear acceptance criteria or undocumented customizations can leave you dependent on the partner after the project ends.
Ask for the subscription tier, the retainer scope and the handover documentation in the quote, and confirm which of these are one-time and which recur.
A commercial SaaS intranet is subscribed per user and hosted by the vendor. Setup and configuration are usually lighter at the start, but the fee continues every period and scales with every seat, including employees who rarely log in. The vendor controls the hosting location, upgrade schedule and feature roadmap, and your options for integrating with internal systems depend on what the vendor exposes.
- Per-seat fees: Each additional employee adds to the recurring bill, so cost grows with headcount and with any contractors or frontline staff you add.
- Vendor-controlled upgrades: Release timing and feature changes follow the vendor's schedule, which affects testing and change control in regulated sectors.
- Data residency: Where employee profiles, posts and files are stored must be confirmed in the contract, including sub-processors and backup locations.
- Integration limits: Connections to your directory, document systems and mobile device management depend on vendor connectors and their terms.
- Typical risk: Lock-in and exit cost. Moving content and profiles out of a SaaS intranet later can be expensive, so confirm export formats before signing.
Ask the vendor to price a three-year view at your current and projected headcount, and to state in writing how you would export all content and user data at exit.
What moves intranet cost up or down
Intranet cost is set less by the software license than by a handful of decisions made early: how many people sign in, which directory and single sign-on features they need, how much content moves over, and what the organization must retain and log. Each driver below maps to a specific cost line, so the quote you request should price each one separately.
User count and tier thresholds
Subscription tiers change at fixed user counts, so headcount determines which line item you pay for. XWiki Pro and support plans list Starter (up to 25 users, XWiki Cloud only), Basic (up to 1,000 users), Business (up to 10,000 users) and Enterprise (unlimited users). Nextcloud Enterprise has a 100-user minimum. Confirm whether your count includes contractors, shift workers and inactive accounts, and ask how a partner counts users for renewals.
Directory and SSO edition needs
Whether LDAP, Active Directory, SAML or OpenID Connect is included in your edition is a cost decision, not a configuration detail. Nextcloud documents LDAP and Active Directory login plus OpenID Connect and SAML backends, but confirm which of these your chosen edition supports without extra licensing. XWiki Pro lists Active Directory and Azure Active Directory SSO applications. Price the identity provider work separately from the intranet license.
Spaces, integrations and connectors
Every space with its own permission model, and every connection to a document store, mail system or ticketing tool, adds design, testing and maintenance effort. Connectors such as the Google Apps, Office365 and OnlyOffice connectors in XWiki Pro are priced in the subscription, while custom integrations are scoped by the partner. Ask for a list of spaces and integrations in the written scope, and a rule for who approves new ones after go-live.
Content volume and migration
Migration cost rises with the number of pages, attachments, users, permissions and history you keep. Confluence Migrator Pro from XWiki SAS keeps page history but not attachment history, and is priced from 2000 EUR with a trial limited to 30 pages per migration. SharePoint and legacy portal moves need separate analysis. Ask the partner which content is cleaned or archived before the move, because stale content costs money to migrate and little to use.
Mobile and frontline access
Mobile access and frontline reach add cost through app configuration, device management and identity options for staff who have no corporate email. If many workers sit outside the directory, you may need a separate sign-in path, shared kiosks or a licensed mobile model. Confirm with the vendor which mobile clients and push features your edition includes, and whether push notifications rely on external services that your security team must approve.
Retention and audit logging obligations
Retention and audit requirements drive storage, backup and log retention costs, and they can prompt a higher edition or extra tooling. Regulated sectors may need records kept for defined periods, for example SEC Rule 17a-4(b)(4) requires broker-dealers to preserve certain business communications for not less than three years. HIPAA requires audit controls on systems holding ePHI under 164.312(b). Ask the partner to price log retention, backup testing and any legal hold feature as explicit line items.
Which intranet costs are one-time and which recur every year
The one-time costs of a self-hosted intranet are the work that gets the platform to a usable state: installation, theming, directory and single sign-on integration, content migration and the first round of training. Each of these is paid once, but the amount depends on scope. Identity is the item most often underestimated. Nextcloud's LDAP app, for example, lets Active Directory users log in with their directory credentials, and OpenID Connect or SAML backends are also documented, but which of these your edition supports and how group mapping should work are questions to settle in writing before any quote is accepted. Migration effort follows the same logic: ask for a content inventory that separates what moves from what is retired.
The recurring costs are the ones that keep appearing in the budget. They include hosting, any vendor subscription or maintenance fee, upgrades, administration, and moderation time spent by internal staff who approve, archive and answer posts. Upgrades are the cost most often left out of comparisons. Nextcloud publishes a new major version every four months and supports each one for one year, so an organization that wants to stay supported will repeat the upgrade cycle several times a year. Nextcloud also does not allow skipping major releases, so each upgrade must move one major version at a time, with a backup taken before every step and third-party apps disabled until confirmed compatible. Plan the labor for those steps as a standing line item, not a project.
When you compare quotes, ask each provider to split the figure into one-time and annual amounts, name the upgrade path it assumes, and state who performs each backup and test restore. Confirm whether the release cadence you are quoting matches the support window you need, because a stable line on a longer support cycle changes the frequency of this work. Vendor subscription tiers, such as the Nextcloud Enterprise tiers that list per-user annual rates from 100 users, should be checked against your actual headcount and the support hours you expect. Those figures recur every year and often outweigh the one-time spend over a multi-year horizon.
How to build your own intranet cost estimate
This sequence turns vague budget assumptions into a scoped, comparable set of quotes, so you can total the cost of a self-hosted intranet, a partner-led build and a per-user SaaS intranet over the same support window.
Count named and active users by tier
Start by counting named employees, then separate active users (those who log in or post in a typical month) from licensed seats. Break the count into tiers such as frontline, office, contractors and external partners, because subscription tiers and per-user pricing are set on these numbers. Owner: the HR or IT lead with access to the directory. Done when you have one table of named and active counts per tier, with the growth expected over the planned support window noted separately.
List spaces, audiences and posting rights
Map every intended space, team site, news channel and audience group, and record who may read and who may publish in each. Edition choice and module needs often depend on these rules, for example whether mandatory read notices or targeted news are required. Owner: the communications lead with business unit representatives. Done when each space has a named owner, an audience definition and a publishing rule that you can hand to a vendor or partner.
Inventory content and legacy portals to migrate
List every legacy intranet, shared drive area, wiki and document library that will move, with page or file counts, attachment sizes and the content owners who will approve what stays. Migration effort tends to be one of the least predictable cost lines, so flag any source system that needs a paid migration tool or custom export. Owner: the content owner with IT support. Done when you have an inventory that marks each item as migrate, archive or retire, and a list of the source platforms involved.
Define identity and SSO requirements
Document how users sign in today, including Active Directory or LDAP, existing SSO, multi-factor requirements and any external accounts for contractors. Check which of these the candidate platform supports in the edition you are considering, since directory and SAML or OpenID Connect integration are often gated behind paid editions or extensions. Owner: the identity or security architect. Done when you have a written identity specification and a list of features to confirm in writing with each vendor or partner.
Choose the hosting model
Decide whether the intranet will run in your own cloud account, your data center, a vendor-hosted cloud, or a partner-managed environment. Each choice moves costs between infrastructure you pay for directly, licensing for hosting services, and staff time for patching, backup and monitoring. Owner: the platform or infrastructure lead. Done when the hosting model is approved, the required database, caching, backup and high-availability components are listed, and the cost lines for each are identified.
Decide on the support level
Choose the vendor support tier or retainer you need for the planned window, including response expectations, upgrade assistance and security patch handling. Support contracts often include tiers that differ on maintenance length, support hours and response times, so compare those terms directly. Owner: the CIO or head of IT with procurement. Done when the chosen support level is written down with the reasons for it, and the alternative support options are recorded for comparison.
Estimate moderation and admin hours per month
Estimate the recurring effort for content moderation, space administration, user onboarding, theming changes, upgrades and backup checks, and assign each task to an internal role or to a partner. Ongoing moderation is usually a staffing decision rather than a licence line, so model it as hours per month by role. Owner: the intranet product owner with the communications and IT leads. Done when you have a monthly effort table that you can compare across build, partner and SaaS options.
Request written quotes and compare total cost
Send the same written scope to each candidate: self-hosting with an internal team, a partner-led implementation, and a per-user SaaS intranet. Ask each quote to list one-time items (setup, theming, migration, training) separately from recurring items (subscriptions, hosting, support, moderation support, upgrades), and to state the user tier and support window it assumes. Compare the total cost over the planned support window rather than the first-year licence line alone. Done when every option is priced against the same scope and you can show the total for each.
Common questions about intranet cost and effort
What drives the total cost of a self-hosted intranet?
Total cost is driven by who does the work and how many users and spaces you run. The main components are infrastructure (servers, database, backups, storage), software licensing (free community editions or paid editions such as XWiki Pro or Nextcloud Enterprise), implementation work (installation, directory integration, theming, content migration), and ongoing operations (upgrades, moderation, support). Licensing is only one line. Edition tiers in the supplied pricing are set by user count: XWiki's Starter, Basic, Business and Enterprise tiers are sized to 25, 1,000, 10,000 and unlimited users, and XWiki SAS states cloud and on-premises pricing is the same. Ask any vendor or partner for a quote that separates one-time work from recurring fees, and check the user count and edition each line assumes.
Is a self-hosted intranet cheaper than a per-user SaaS intranet?
It depends on user count, the features you need, and how much internal staff time you can commit. Per-user SaaS pricing scales linearly with headcount and usually bundles hosting and upgrades. A self-hosted build moves that cost into infrastructure, licenses and labor, which can be lower for large audiences but is not automatically cheaper once you count operations. For a sense of how per-user pricing scales, Nextcloud Enterprise lists Standard, Premium and Ultimate tiers at 71.29, 104.99 and 204.75 euros per user per year for 100 or more users, according to Nextcloud's pricing page. Build a like-for-like model over three to five years with your actual user count, directory needs and support requirements, and compare it with SaaS quotes that state the same scope.
How long does intranet onboarding take, and what does it depend on?
No duration is given here unless it is confirmed in a written scope, because the timeline depends on the work agreed. The main variables are the number of audiences and spaces, the identity source (for example, whether LDAP or Active Directory users must log in with their directory credentials, which Nextcloud documents through its LDAP app), whether SSO needs a paid edition, the volume and quality of content to migrate, theming and branding requests, and the number of approvals needed from HR, legal and communications. Ask the partner to break the timeline into phases with named deliverables and acceptance criteria, and to list what the client must provide, such as directory access, content owners and test users.
Can our internal team run a self-hosted intranet without a partner?
A small team with Linux, database and web server skills can run a community edition, but the operating load is ongoing. Upgrades are the most common surprise. Nextcloud does not allow skipping major releases, so administrators must upgrade one major version at a time, back up before each upgrade and disable third-party apps until they are confirmed compatible. Nextcloud publishes a new major version every four months and supports each for one year, so the upgrade calendar never stops. Staff also need to handle backups, patching, monitoring, access reviews and user support. Assess these tasks against the people you have today. A partner can take on part or all of them under a fixed-scope or retainer agreement, and DeployOpen offers ongoing support, upgrades and continuous testing as retainers.
What does an intranet project need from HR and communications?
HR and communications own the content rules, audiences and sign-off, so their time is often the real constraint. HR typically supplies the employee directory data, joiner and leaver processes, and policy documents that must be migrated or linked. Communications sets the spaces, news standards, moderation roles and the adoption plan. Both teams should agree early on who can post where, which content is mandatory to read, how comments are moderated, and what is retired from the old portal or email. Ask the implementation partner to name these decisions in the written scope and to plan review cycles, because unresolved decisions usually delay theming, migration and rollout more than technical work does.
When is a vendor support subscription worth paying for?
A support subscription is worth comparing when you need guaranteed response, enterprise features or a lifecycle longer than a community release gives you. Support tiers differ in what they cover. XWiki's support and Pro subscriptions are sized by user count, and XWiki consulting is listed at 1200 euros per day but requires a Business or Enterprise support plan, according to XWiki's pricing page. Nextcloud's Premium tier adds a maintenance lifecycle of five or more years, and its Ultimate tier adds support up to 24/7 with response times down to one hour, according to Nextcloud's pricing page. Compare these vendor terms with the response, lifecycle and feature needs written into your own risk assessment, and confirm any SLA in writing before you rely on it.
Which intranet costs are one-time and which recur each year?
One-time costs cover planning, installation, directory and SSO integration, theming, content migration and initial training. Recurring costs cover hosting and storage, backups, subscription or support fees, upgrades, security patching, and moderation or content maintenance by staff. Migration is often the largest one-time item when a large legacy portal must be moved, and XWiki's Confluence Migrator Pro, priced from 2000 euros with a trial limited to 30 pages per migration per XWiki Store, shows that migration tools carry their own licensing. Ask each quote to label every line as one-time or recurring, state the billing unit, and name the assumptions behind hours and user counts.
What should a quote for intranet work include?
A useful quote lists the written scope, deliverables, assumptions, exclusions and acceptance criteria before it lists prices. DeployOpen works to fixed-scope engagements where scope, deliverables and timelines are agreed in writing before work starts, and it does not publish a price list. Expect the quote to name the platform and edition, user count, hosting location, integrations (directory, SSO, document systems), migration volume, theming work, training and handover, and any retainer for later support. Ask what the client must provide and what changes would be billed separately. Include an illustrative example in your own evaluation, such as a pilot space for one department, to test the assumptions before you approve a full rollout.
How DeployOpen scopes and delivers a fixed-scope intranet implementation
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 intranet cost decisions, we start from a written scope that separates one-time build work from recurring hosting, licensing and moderation effort, so the total cost can be compared fairly against per-user SaaS options.
How we scope
- Engagements are fixed-scope, with the platform, edition, user count and integrations agreed in writing before work starts.
- We list which cost lines the scope covers, such as hosting setup, theming, directory integration and content migration, and which sit with your team.
- We ask for your user counts by audience, directory source, and any subscription or support tier you expect to need.
How we build
- We install the chosen platform in your cloud account, data center or air-gapped network, following the vendor's supported system requirements.
- We configure directory integration, single sign-on and theming against your brand, then test access by role and audience.
- We run content migration in agreed batches and test permissions, search and mobile access before any launch date is set.
How we hand over
- You receive architecture documentation, configuration records, runbooks for backup and restore, and an upgrade procedure.
- We document the recurring cost drivers, including licensing tiers, hosting capacity and moderation roles, so finance and IT can track them.
- Knowledge transfer sessions cover administration, moderation and the upgrade path, so your team can operate the intranet without us.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, separate from the fixed-scope build.
- Retainer scope, response expectations and upgrade handling are written out, so you can compare them with a vendor support tier.
- Before each major platform upgrade we agree the test plan, backup approach and any third-party app compatibility checks.
