Service Delivery Hub

Cloud operations without the operational complexity.

The Forrit Service Delivery Hub is the management and orchestration layer behind the Forrit Platform. It standardises how Forrit environments are provisioned and managed, turning cloud infrastructure into a repeatable platform operation instead of a bespoke engineering project for every deployment.

Illustration: the Service Delivery Hub showing each environment in an estate with its status and upgrade plan, a production upgrade scheduled in a change window, and monitoring and cloud cost summaries.

01 · Automated provisioning

From infrastructure engineering to platform operations.

Without a platform layer, every new CMS environment becomes a cloud engineering project: resources to design, configure, secure and document, often slightly differently each time. The Service Delivery Hub automates the provisioning of CMS environments and their associated infrastructure, so creating an environment becomes a repeatable operation.

Provisioning gives you a configured CMS environment, ready for your teams. Building or migrating the websites that run on it is a separate piece of work, but it starts from the same consistent, governed foundation every time.

How an environment is provisioned

  1. Request the environment you need, such as test, staging or live

  2. The Hub provisions the CMS environment and its supporting infrastructure

  3. The same configuration standards are applied every time

  4. The environment appears in the Hub, visible alongside the rest of your estate

Illustration: a standard environment definition, covering the CMS, Web and JSON delivery, edge protection and monitoring, provisioned by the Service Delivery Hub into matching test, staging and live environments.

Provisioning capabilities

  • Automated provisioning

    A simple seven-step process implements the CMS and makes sure the entire environment is created accurately.

  • Standardised environments

    Environments are created the same way every time rather than configured by hand, so each deployment starts from the same standard.

  • Safe publishing lifecycle

    Test, staging and live environments, task branches and full rollback let many teams work in parallel without risking production.

02 · Central visibility

See every environment in one place.

As an estate grows, operational information tends to scatter across consoles, tools and teams. The Service Delivery Hub brings it together: technical teams can access environment information, operational logs, security reporting and cost information for the environments supporting Forrit, from one place.

    Illustration: a Service Delivery Hub view with environment health, recent operational log entries, the latest security report and a monthly cloud cost chart.

    Visibility capabilities

    • One dashboard for the estate

      Monitor and manage your entire web estate from a single interface, with full platform performance diagnostics.

    • Real-time monitoring and alerts

      Global real-time monitoring identifies performance issues quickly, and system alerts tell you when a service isn't working as expected.

    • Operational logs

      Access operational logs for your environments to investigate issues and support audits.

    • Security reporting

      Review security reporting for your environments alongside the rest of their operational information.

    • Real-time cost tracking

      See your cloud costs as they happen, and auto-scale environments so you only pay for the services you need.

    03 · Managed upgrades

    Stay current without disruptive upgrade projects.

    Falling behind on CMS versions creates risk, but upgrades can be disruptive. The Service Delivery Hub supports the management of CMS versions and automated upgrade processes that can be aligned with your organisation's change windows.

    Every Forrit product release is penetration tested before it reaches you. Read more about our secure development lifecycle.

    How an upgrade runs

    1. Each new Forrit release is penetration tested before it is made available

    2. The upgrade is planned into an agreed change window

    3. The Hub runs the upgrade through an automated process

    4. The CMS version of every environment stays visible in the Hub

    Illustration: CMS versions across test, staging and production environments, with the production upgrade scheduled inside an agreed Saturday change window.

    Upgrade capabilities

    • CMS version management

      See which CMS version each environment is running and manage versions centrally, across the whole estate.

    • Aligned with your change windows

      Automated upgrade processes can be aligned with the change windows your organisation agrees.

    • Managed patching and upgrades

      Vulnerability scanning feeds managed patching and upgrades, so no environment in your estate falls behind.

    • Penetration-tested releases

      Every Forrit Platform product release is penetration tested. Optional penetration testing is available for your own environments too.

    04 · Complex estates

    One operating model for the whole estate.

    The Service Delivery Hub provides an operational layer across all the environments supporting your Forrit deployment. Within a CMS environment, multiple projects can represent websites, APIs or other digital destinations, so a group can run many brands, sites and channels without a separate operating model for each.

    See how this supports scaling operations as your estate grows.

      Illustration: one production CMS environment containing several projects, a corporate website, two brand sites, mobile app content, a partner API and a campaign microsite, each with its own team and workflow, all managed through the Service Delivery Hub.

      Estate capabilities

      • Multi-tenancy

        Run one site or a thousand from one platform, with projects that group the content and endpoints for each site, brand or business unit.

      • Onboard new business units

        Bring new departments, partners or acquired businesses into your estate while keeping control of your brand.

      • Dynamic auto-scaling

        Environments scale to meet surges in traffic, so performance stays consistent and you only pay for the cloud services you actually need.

      05 · Your choice of cloud

      Cloud native. Run it where you need it.

      The Forrit Platform is cloud native. Deploy it on leading public cloud platforms or with sovereign cloud providers to meet data residency and regulatory requirements, or run your Forrit environment in your own cloud tenant and subscription.

      Whichever model you choose, the platform's seven layers of security come as standard, and in your own tenant you can add your existing security controls around it.

        Illustration: the Forrit Platform, made up of Forrit CMS and the Service Delivery Hub, running on public cloud, sovereign cloud or your own cloud tenant, with your own optional security controls around it.

        Cloud capabilities

        • Cloud native and containerised

          A platform-as-a-service architecture with modern containerisation and resource management, optimised for performance and cost.

        • Public or sovereign cloud

          Deploy on leading public cloud platforms or with sovereign cloud providers to meet data residency and regulatory requirements.

        • Your cloud, your ownership

          Your Forrit environment can live in your own cloud tenant and subscription. You own the resources, your assets stay in your subscription and you keep control of perimeter security, including any extra layers you add around Forrit.

        • In your tenant

          Add your own layers

          Seven layers come as standard. Run Forrit in your own cloud tenant and you can surround it with the controls your security team already uses, such as firewalls, intrusion detection and network monitoring.

        A repeatable foundation

        Spend engineering effort on experiences, not infrastructure.

        The Service Delivery Hub turns the cloud infrastructure behind a CMS estate into a repeatable, governed platform capability. Instead of rebuilding the operational model every time you need another site, service or environment, you reuse the same foundation and focus engineering effort on the digital experience itself.

        • Product

          Forrit CMS

          Create, govern and reuse content across your digital estate, with structured content, visual page building and headless delivery in one CMS.

          • Structured content
          • Reusable components
          • 550+ locales
        • Platform

          The Forrit Platform

          See how Forrit CMS, the Service Delivery Hub and your digital experiences fit together on one secure platform.

          • Key benefit

            Security

            Seven layers of protection, from edge security and Airlock Publishing to secure development and ISO 27001 assurance.

            Service Delivery Hub questions, answered

            Want to see it in action?

            Book a demo