Which open-source enterprise CMS fits your organization
If you are a large organization shortlisting self-hosted CMS platforms for multi-site, multilingual or regulated content, the choice usually comes down to three questions: which license your legal team will accept, how long each release line stays supported, and which team will run it. Drupal, TYPO3 and Umbraco are all credible enterprise options, and none of them is a paid-only product at its core. Choose Drupal when you want a GPL-2.0-or-later platform on PHP with broad database support (MariaDB, MySQL, PostgreSQL and SQLite are core options, with Microsoft SQL Server and MongoDB through contributed modules) and a large contributed ecosystem, including the samlauth module for SAML service provider authentication. Choose TYPO3 when your editorial model is built around tree-structured sites and you want GPL-2.0-or-later licensing with LTS windows: free support for v13.4 runs until 2027 and v14.3 until 2029, after which paid Extended Long Term Support applies.
Choose Umbraco when your team works in .NET and you want an MIT-licensed core with LTS releases. Umbraco 17 is the current LTS line, with end of life on November 27, 2028 and extended support until November 27, 2030. Keep the licensing boundary clear: add-ons such as Umbraco Engage and Umbraco Forms are licensed separately from the MIT core, and Forms requires a valid license on any public domain. Umbraco Cloud is optional, and if you adopt it, confirm the hosting terms with Umbraco directly. If your team is built on Python and Django, Wagtail is the option to evaluate in this group. It is BSD-3-Clause licensed and offers LTS versions, so confirm which release line and support window match your upgrade policy before you commit.
Which CMS fits which enterprise scenario
This table maps common enterprise scenarios to the platform that usually fits best, the reasons behind that fit, and the conditions that would change the choice. Read each row against your own runtime standards, support calendar and content team skills, because the same scenario can point to different platforms once those constraints are fixed.
| Scenario | Best fit | Why | Condition that changes the choice |
|---|---|---|---|
| Multi-site governance on one codebase | Drupal | Drupal's multisite and distribution model lets one core and shared modules serve many sites, with each site configured separately. Drupal CMS adds recipes and site templates for teams that want repeatable setup. | If your sites need very different editorial workflows, or your team lacks Drupal developers to maintain a shared codebase, a TYPO3 or Umbraco setup may be simpler to govern. Confirm multisite behavior against your own architecture. |
| Multilingual publishing | Drupal or TYPO3 | Both have mature content translation capabilities in core or established extensions, which suit large content estates with many languages. Confirm the exact translation workflow and extensions your editors need. | If translation workflow depends on a third-party translation management system, verify the integration on the platform you shortlist. Choose on proven workflow fit, not on the language count alone. |
| .NET shops with existing Microsoft infrastructure | Umbraco | Umbraco is a .NET CMS published under the MIT license, and current documentation requires .NET 10.0 or higher. It supports SQLite or SQL Server, so it fits teams already running Microsoft stacks. | If your hosting standard is Linux only, or you need Umbraco Forms or Engage on public domains, budget for the licensing model and confirm terms with Umbraco before committing. |
| PHP or Linux-centric teams | Drupal or TYPO3 | Drupal 11 requires PHP 8.3 or later and supports MariaDB, MySQL, PostgreSQL and SQLite. TYPO3 14 requires PHP 8.2.0 up to 8.5.99 and Composer 2.1 or higher, so both fit a Linux and PHP operations model. | Drupal 12 requires PHP 8.5 or later, so plan PHP upgrades against the release schedule. Confirm your database choice, since Microsoft SQL Server for Drupal depends on contributed modules. |
| Python and Django teams | Wagtail | Wagtail is a BSD-3-Clause Django CMS, so teams with Python skills can extend it with the same framework they already run. This keeps the content layer inside an existing engineering practice. | If your editors need an enterprise visual page builder out of the box, or your team has little Python experience, Drupal or Umbraco may suit better. Confirm Wagtail's support windows against your own standards. |
| Marketing-led teams wanting visual page building | Drupal (Drupal CMS) | Drupal CMS is a distribution for marketers and content teams, with recipes, site templates and the Drupal Canvas visual page builder. It is the option in this comparison that names a visual builder as part of its current offering. | If you need strong marketing automation, personalization or A/B testing, Umbraco Engage is a licensed add-on with its own domain licensing terms. Confirm whether Drupal Canvas meets your page-building needs before choosing. |
| Teams with a legacy Drupal 7 or older site | Migration to a supported Drupal version | Drupal 6 and 7 sites cannot simply be updated to Drupal 10 or later. They are migrated into a new site using the core Migrate modules or Drush, and themes must be rebuilt. Drupal 7 security support ended on January 5, 2025. | If migration cannot happen soon, the Drupal Association's Extended Security Support Provider Program lists HeroDevs and Tag1 Consulting as certified vendors. Confirm scope and cost with each provider. Drupal 10 reaches end of life on December 9, 2026. |
How license and LTS windows differ across the three platforms
The license governs the code you receive, and Drupal, TYPO3 and Umbraco differ most in how their support windows are structured. Drupal core and contributed files derived from it are licensed under GPL-2.0-or-later, and TYPO3 CMS is under GPL version 2 or later. Umbraco CMS is MIT-licensed and Wagtail is BSD-3-Clause. No license of these types promises security patches, support windows or upgrade paths. TYPO3's licenses page states that TYPO3 and installed extensions form a single combined program, so extensions fall under GPL and may be sold as long as the license terms are not changed. Drupal has no paid edition of core, so the license itself costs nothing, but contributed modules carry their own maintenance risk. Umbraco Forms and Umbraco Engage are separate paid add-ons, licensed per domain, so count your production and development domains before you commit.
Support windows are where the platforms diverge most. Drupal 10 reaches end of life on December 9, 2026, and Drupal 12 is scheduled for the week of December 7, 2026, so a Drupal 10 estate has a short planning window. Drupal 7 security support ended on January 5, 2025, and the Drupal Association lists HeroDevs and Tag1 Consulting as certified vendors for sites that cannot migrate yet. TYPO3 14 is the LTS release for new projects, with v13.4 free support ending in 2027 and v14.3 free support ending in 2029. Paid Extended Long Term Support (ELTS) applies after free support ends. Umbraco 17 is LTS through November 27, 2028, with Extended Long-Term Support to November 27, 2030. Umbraco 13 reaches end of life on December 14, 2026.
Check the version you run today before comparing features. A Drupal 10 or Umbraco 13 site has months, not years, before end of life, and a Drupal 6 or 7 site cannot be updated in place, so plan a migration into a new site with the core Migrate modules or Drush, and rebuild its themes. Ask each vendor in writing what extended support costs, who pays for it, and whether it covers the modules and extensions you rely on. Confirm the current Wagtail LTS dates with the Wagtail project before you plan. DeployOpen does not publish prices, so ask for a quote that lists extended support and upgrade work as separate line items from the initial build.
How Drupal, TYPO3 and Umbraco differ on multi-site, multilingual and add-ons
Drupal's multi-site and multilingual approach is delivered through its core and contributed module ecosystem rather than a single built-in product. The supplied facts confirm that Drupal 11 runs on MariaDB, MySQL, PostgreSQL or SQLite, which constrains how a multi-site estate shares or separates its databases, and that contributed files on Drupal.org are GPL-2.0-or-later. For identity, the contributed SAML Authentication module (samlauth) lets a site act as a SAML service provider, and its latest stable release 8.x-3.14 supports Drupal 10.3 and later and Drupal 11. The contributed OpenID Connect module authenticates users from external providers and creates accounts on first sign-in, with built-in clients for generic OAuth 2.0, GitHub, Google, LinkedIn, Facebook and Okta.
- Add-on model: Extensions are contributed modules and themes, all under GPL-2.0-or-later, with no paid edition of Drupal itself.
- Identity: samlauth and OpenID Connect are the supplied options, each with its own module maintenance and configuration.
- Multi-site: Confirm how your chosen modules and hosting pattern handle shared codebases, separate databases and per-site configuration.
- Multilingual: Confirm the language modules, translation workflow and content model you need against your current Drupal version.
- Upgrades: Contributed modules must support your target Drupal version, so check module compatibility before each major upgrade.
Confirm with your implementation partner which contributed modules your sites require, and test samlauth or OpenID Connect against your identity provider before committing.
TYPO3 is licensed under GPL v2 or later, and its licenses page states that TYPO3 and installed extensions form a single combined program, so extensions fall under the same license. Extensions may be sold as long as the license terms are not changed, which gives vendors a commercial extension market without a proprietary core. The supplied facts do not describe TYPO3's multi-site or multilingual features in detail, so those capabilities must be confirmed against the TYPO3 14 documentation and your own test environment before you rely on them.
- Add-on model: Extensions share the core's GPL license, and paid extensions are allowed as long as their license terms are unchanged.
- Release track: TYPO3 14 LTS at version 14.3.9 is the release listed for new projects, with free support for the 13.4 and 12.4 tracks on their published end dates.
- Database and runtime: TYPO3 14 supports MariaDB, MySQL, PostgreSQL and SQLite, and requires PHP 8.2.0 up to 8.5.99.
- Extended support: Paid Extended Long Term Support (ELTS) applies to versions after their free support ends, so budget for it on older tracks.
- Multi-site and multilingual: Confirm the site-tree, language and translation features in your target version, along with how your extensions handle them.
Ask for a written list of the extensions your estate requires, their license terms, and their support status on the TYPO3 version you plan to run.
Umbraco is a free and open source .NET CMS published under the MIT license, with Umbraco Cloud available as a managed service on Microsoft Azure. Its add-ons are licensed separately, and the licensing terms differ by product, so read each add-on's license before assuming it is included. The supplied facts confirm that the Content Delivery API returns content as JSON for headless use, is opt-in, and serves protected content only when member authentication is enabled. Multi-site and multilingual capabilities are not detailed in the supplied facts, so confirm them against current Umbraco documentation.
- Umbraco Forms: Runs unrestricted locally but requires a valid license on a public domain. Licenses are sold per domain, cover subdomains and include two development or testing domains, with one license per installation.
- Umbraco Engage: Running it on a public domain requires a valid license covering one production domain and up to two development or testing domains.
- Umbraco Cloud: Provides Development, Staging and Live environments, automatic backups and a global CDN on Azure, with Umbraco Deploy for synchronizing content and structure.
- Identity and API: The Content Delivery API requires explicit configuration and an API key for unpublished preview content.
- Multi-site and multilingual: Confirm these features and their licensing against current Umbraco documentation before you plan the estate.
Confirm the number of public domains and development domains each add-on must cover, since per-domain licensing drives the recurring cost.
Side-by-side capability across the enterprise CMS options
This table compares Drupal, TYPO3, Umbraco and Wagtail on license, runtime, databases, support windows, paid add-ons, managed hosting, API delivery and identity integration. Where a supplied fact is missing for a cell, the cell says what to confirm with the vendor. Use it to shortlist, then check the support dates against your own upgrade calendar.
| Capability | Drupal | TYPO3 | Umbraco | Wagtail |
|---|---|---|---|---|
| License | GPL-2.0-or-later. No paid edition of Drupal itself. | GPL v2 or later for the core and installed extensions. | MIT for the Umbraco-CMS repository. Engage and Forms are licensed add-ons. | BSD-3-Clause. Confirm current terms with the Wagtail project. |
| Core language and runtime | PHP, on Apache, Nginx or other web servers. | PHP, with Composer 2.1 or higher. | C# on .NET. | Python on Django. Confirm supported Python and Django versions. |
| Minimum PHP or .NET requirement | Drupal 11 needs PHP 8.3 or later. Drupal 12 needs PHP 8.5 or later. | TYPO3 14 needs PHP 8.2.0 up to 8.5.99 and at least 256 MB of RAM. | Current documentation requires .NET 10.0 or higher. | Not a PHP or .NET platform. Confirm the Python version for your target release. |
| Supported databases | MariaDB 10.6+, MySQL 8.0+, PostgreSQL 16+, SQLite 3.45+. SQL Server and MongoDB via contributed modules. | MariaDB 10.4.3+, MySQL 8.0.17+, PostgreSQL 10.0+, SQLite 3.8.3+. | SQLite and SQL Server are documented. Confirm other options with Umbraco. | Confirm supported databases with the Wagtail project for your version. |
| LTS or support model | Major versions about every three years. Drupal 10 end of life is December 9, 2026. Drupal 12 is scheduled for the week of December 7, 2026. | LTS releases. v12.4 free support ends in 2026, v13.4 in 2027, v14.3 in 2029. Paid ELTS follows. | LTS releases. Umbraco 17 ends November 27, 2028, with XLTS to November 27, 2030. | Quarterly feature releases with LTS versions. Confirm current LTS dates and length. |
| Paid add-ons | No paid Drupal edition. Extended security support for legacy sites comes from providers listed by the Drupal Association. Confirm terms. | ELTS for versions past free support. Extensions can be sold if license terms stay unchanged. | Engage and Forms need a license per production domain. Forms licenses also cover subdomains. | Confirm commercial add-ons and support contracts with the Wagtail project or partners. |
| Managed hosting option | No vendor-run hosting in the supplied facts. Confirm with hosting providers and Drupal service firms. | Confirm managed hosting options with TYPO3 partners. | Umbraco Cloud is managed hosting on Microsoft Azure, with staging and live environments. | Confirm managed hosting options before choosing a self-hosted path. |
| Headless or API delivery | Confirm the API modules and version support for your use case. | Confirm headless delivery options for your TYPO3 version. | Content Delivery API returns JSON. It is opt-in and needs configuration. | Wagtail's API support depends on the version and packages. Confirm with the project. |
| Identity integration | SAML service provider module (samlauth 8.x-3.14) and OpenID Connect module with Okta, Google and GitHub clients. | Confirm SSO modules and extension support for your environment. | Member authentication protects content. Confirm SSO connectors with Umbraco or partners. | Confirm SSO packages and their maintenance status before committing. |
Each option in brief, with its license
Each card names the license, the support model and the team that tends to fit best. It also names one condition that would rule the option out. Read the license and support terms before you compare features, because they set who pays for upgrades and fixes.
Drupal
Drupal core and contributed files hosted on Drupal.org fall under GPL-2.0-or-later. There is no paid edition of Drupal itself, so your cost sits in hosting, integration, module maintenance and any support contract you choose. Drupal CMS is a distribution built on core for marketing teams, with recipes, site templates, the Drupal Canvas page builder and optional AI tools. Best fit: multi-site, multilingual estates with in-house Drupal developers. Ruled out if your team cannot keep contributed modules current with the core release cadence, since Drupal 10 reaches end of life on December 9, 2026.
TYPO3
TYPO3 CMS is licensed under GPL v2 or later and represented by the TYPO3 Association. TYPO3 and its installed extensions form one combined program, so extensions fall under the GPL too, and they may be sold as long as the license terms stay unchanged. Free LTS support is listed on the roadmap, and paid Extended Long Term Support (ELTS) applies to versions after free support ends. Best fit: enterprise and public sites that want a planned LTS line and can budget for extension maintenance. Ruled out if you need one vendor contract covering the core and every extension in your stack.
Umbraco
Umbraco is a free and open source .NET CMS published under the MIT license. Its paid add-ons are licensed separately: Umbraco Forms and Umbraco Engage each need a valid license to run on a public domain, sold per domain. Umbraco Cloud is a managed service on Microsoft Azure with Development, Staging and Live environments. Best fit: .NET teams already running Azure or Windows estates that want LTS releases and an optional managed host. Ruled out if your forms or marketing features must run without per-domain license tracking, or if your team has no .NET skills to maintain the platform.
Wagtail
Wagtail is a Django CMS released under the BSD-3-Clause license, which permits commercial use with attribution and imposes no copyleft obligation. It ships quarterly feature releases alongside LTS versions, so you choose between following new features and staying on a stable line. Best fit: Python teams with Django experience that want the CMS in the same codebase and deployment pipeline as their application. Ruled out if your team has no Python or Django capacity to own upgrades, or if your requirements depend on a large catalog of packaged modules for multi-site governance. Confirm the features you need against its documentation.
What running each CMS costs in staff time and upgrades
The license line is rarely the largest cost. Drupal core is licensed under GPL-2.0-or-later with no paid edition, and TYPO3 CMS is also GPL, so neither core carries a license fee. Umbraco's MIT-licensed core is free too, but its Engage and Forms add-ons need a valid license for each public domain, and TYPO3 Extended Long Term Support (ELTS) is a paid service for versions after free support ends. Most of the recurring spend sits elsewhere: hosting and infrastructure, the staff who patch and monitor the stack, contributed modules or extensions, theme work, and any paid support window. When you request a quote, ask the partner to split one-time build cost from recurring run cost, and to state which support window each figure assumes.
Upgrade effort scales with sites, languages, custom code and version jumps. Each additional site, language or custom module or extension multiplies the regression testing and the chance that an upgrade breaks something. A PHP or .NET version jump can be the expensive part, since the platform, its modules and the hosting image all have to move together. Check the support dates in each vendor's roadmap (Drupal 10 reaches end of life on December 9, 2026, and Umbraco 13 on December 14, 2026) and price the upgrade you will actually face, not the one you hope for. Ask for the number of contributed modules or extensions in scope, the languages and sites covered, and whether the quote includes testing, rollback planning and documentation.
Drupal 6 and 7 are migrations, not upgrades. Drupal.org documentation says those sites cannot simply be updated to Drupal 10 or later. They are migrated into a new site using the core Migrate, Migrate Drupal and Migrate Drupal UI modules or Drush, and themes must be rebuilt because they cannot be migrated. If you run a legacy Drupal 7 estate, budget for content migration, theme rebuilds and re-testing of every integration, and ask whether the Extended Security Support Provider Program is a bridge while the migration proceeds. Confirm with the vendor and your own environment before committing to a date.
How to choose and pilot the right enterprise CMS
This sequence turns a shortlist of Drupal, TYPO3, Umbraco and Wagtail into a scored decision backed by a working pilot, so the choice rests on your sites, identity model and upgrade calendar rather than on feature lists.
List required sites and languages
Start by inventorying every site, subdomain, brand and language the platform must serve, along with the expected number of editors and whether any site needs shared content across domains. Record which sites are public, which sit behind a login and which need a headless API for a separate front end. Ask each vendor and each candidate partner how they handle multi-site and multilingual setups at your scale, and which modules or extensions that depends on. The output is a single requirements sheet that every later step uses, signed off by the content owner and the platform owner.
Map identity and integration needs
Document how editors and visitors will sign in, including whether you need SAML, OpenID Connect or a directory-backed login, and which systems the CMS must call or receive data from, such as CRM, marketing tools, search and payment services. For Drupal, check the contributed SAML and OpenID Connect modules against your identity provider version and the Drupal core version you plan to run. For TYPO3, Umbraco and Wagtail, confirm the equivalent authentication options with the project or the implementation partner. The output is an integration map with an owner and a supported method for each connection.
Check the support window against your upgrade calendar
Build a calendar of your organization's change freezes, audit dates and budget cycles, then compare it with each platform's published support dates. Drupal's core schedule, TYPO3's LTS roadmap and Umbraco's end-of-service policy each set different end dates, and paid extended support exists for some versions. Ask each vendor which version is the long-term release you would start on, when free support ends, and what extended support costs and covers. The output is a dated table showing when each candidate must be upgraded or extended.
Confirm add-on licensing per domain
List every paid or licensed add-on you expect to use, such as marketing, forms or analytics components, and record how each is licensed. Some vendors license per production domain, include a fixed number of development or testing domains, or cover subdomains automatically, and these rules change the cost as you add sites. Ask each vendor in writing how many domains a license covers, whether staging and test environments are included, and whether a license is needed per installation. The output is a licensing matrix that a procurement team can check line by line against the quote.
Run a pilot content model and migration on one site
Choose one representative site and build its content model, templates, roles and workflow on each shortlisted platform, then migrate a sample of real content, including media, URLs and multilingual pages. Record the work each step needed, from modeling to editor training to redirects, and note any module, extension or custom code you had to add. Keep the pilot inside a written scope so the comparison stays fair. The output is a pilot log per platform that shows what was built, what broke and what your team had to maintain afterward.
Score the results against the side-by-side table
Score each pilot against the criteria in the side-by-side comparison table, including license, support windows, multi-site and multilingual handling, identity integration, hosting stack, upgrade effort and the cost of switching later. Weight the criteria using the requirements sheet, so the sites and identity needs carry more weight than features you do not need. Have the platform owner, a security reviewer and a content lead score independently, then reconcile differences in a short review. The output is a signed scorecard with the reasons for each score, plus a list of items to confirm in the written quote before any contract.
Questions buyers ask before choosing an enterprise CMS
Does a free open-source CMS core mean the project costs nothing?
No. The license removes the fee for the core software, but you still pay for hosting, implementation, customization, integrations, security testing, upgrades and ongoing support. Drupal has no paid edition of its core, and the TYPO3 and Umbraco cores are also free to use. Costs that recur include hosting in your own cloud or data center, paid extended support where a platform offers it, and licensed add-ons. Umbraco Forms and Umbraco Engage, for example, require a valid license on a public domain. Ask any implementation partner for a fixed-scope quote that separates one-time build work from recurring operations and licenses.
What drives the effort and time to launch an enterprise CMS?
Effort is driven mostly by scope rather than by the license. The main factors are the number of sites and languages, the content model, the number of integrations (identity, search, analytics, commerce, CRM), the volume and quality of content to migrate, and the number of approval workflows. Migration from an older major version is often the largest item. Drupal 6 and 7 sites cannot be updated in place to Drupal 10 or later and must be rebuilt as a new site, with themes rebuilt as well. Ask for the scope, deliverables and timeline in writing before work starts, since most DeployOpen engagements are fixed-scope.
Can an internal team run a self-hosted enterprise CMS without outside help?
Often yes, if the team already operates PHP or .NET applications, a supported database and a patching routine. The work that tends to stretch small teams is regular core and module updates, security releases, backups, staging environments and performance tuning. Drupal publishes bugfix releases on the first Wednesday of each month and security releases on the third Wednesday, so someone must own that calendar. Confirm that your team can handle the required PHP or .NET version, database and web server. If capacity is thin, a retainer for upgrades, testing and support is one option to price separately from the build.
How should we plan for an upcoming CMS end of life date?
Start with the vendor's published end-of-life date, then decide between upgrading, buying extended support or moving platforms. Drupal 10 reaches end of life on December 9, 2026, with no new Drupal 10 releases after that date, so Drupal 10 sites need a plan to reach Drupal 11 or later. TYPO3 offers paid Extended Long Term Support after free support ends, and Umbraco 13 reaches end of life on December 14, 2026, with its Extended Long-Term Support phase running to December 14, 2028. Umbraco 17 is the current LTS release with end of life on November 27, 2028. Map each dependency, including custom modules and extensions, because those often decide the timeline.
Do Drupal, TYPO3 or Umbraco handle multilingual and multi-site content well?
All three support large, multi-site estates, but the fit depends on how your content is modeled and who manages it. Drupal is widely used for multilingual and multi-site installations and has a large contributed module ecosystem for translation workflows, so the question is mostly about module choice and governance. TYPO3 is built around multi-site trees and is a common choice for multilingual European organizations, though you should confirm language and workflow features against your own requirements. Umbraco supports multilingual content in its .NET stack, and you should confirm the specific translation and domain setup you need. Run a proof of concept with your real languages, approval paths and domain structure before you decide.
When is Wagtail a better fit than Drupal, TYPO3 or Umbraco for a Python team?
Wagtail is the better fit when your engineers already build in Python and Django and want the CMS to live inside that codebase. It is a BSD-3-Clause CMS with quarterly feature releases and LTS versions, so the upgrade path follows the Django stack your team already maintains. Drupal, TYPO3 and Umbraco are stronger when you need a large prebuilt ecosystem of modules, extensions or add-ons, or when your team is already skilled in PHP or .NET. Choose Wagtail if hiring and standards are Python-first. Check its current release and support windows directly before you commit.
What does the work need from our side to start a CMS project?
The work needs named owners, access and decisions. Expect to provide a sponsor who can settle scope, a content owner for the content model and migration, an infrastructure contact for cloud accounts, data centers or air-gapped networks, and a security contact for identity integration, hardening and testing. For identity, confirm whether you need SAML or OpenID Connect and check the module or plugin for your platform. Drupal's contributed SAML and OpenID Connect modules are examples of what to verify. Ask for a written scope listing deliverables, responsibilities and timelines before any work begins.
How DeployOpen scopes and delivers a CMS selection and implementation
DeployOpen plans, implements, customizes, integrates, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure. For an enterprise CMS decision, that means the selection, the build and the handover are scoped together so the platform you choose is one your team can run after the engagement ends.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope names the CMS candidates, sites, languages, licensed add-ons and identity integrations under review.
- Scope also records your hosting target, whether cloud accounts, data centers or air-gapped networks, and the support window you need.
How we build
- We build the chosen platform in your infrastructure, including multi-site and multilingual configuration where the scope requires it.
- Integrations with your identity provider, content delivery and any licensed add-ons are configured and tested against the written scope.
- Hardening, backup configuration and upgrade paths are implemented and tested before the platform goes live.
How we hand over
- Deliverables include architecture notes, configuration documentation and runbooks for the team that will operate the platform.
- Upgrade and end-of-life dates for the chosen version are documented so your team can plan the next change.
- Compliance-readiness evidence is prepared for your assessors, who remain responsible for any audit or certification decision.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after the initial handover.
- Retainers can cover version upgrades, security testing and documentation updates when the platform changes.
- Ask for the retainer terms, response expectations and upgrade responsibilities in writing alongside the fixed-scope quote.
