Platform, Implementation Project, and Production Instance

This page explains the distinction between the platform, an implementation project, and a production instance in Bloomreach Content. Each represents a separate layer within the system and differs in two key ways:

The type of application code, configuration, and data it provides
The party responsible for its development, maintenance, and support

Platform

The Bloomreach Content platform includes the CMS and Repository applications, as well as the HST delivery framework.

The platform also provides standard plugins that extend core functionality.

You can customize and integrate the platform using extension and integration points.

Bloomreach develops, maintains, and supports the platform as a product. For more information, see Bloomreach.

Implementation Project

An implementation project is a software solution built on top of the platform.

An implementation project typically includes:

A content model and document types, defined within the CMS and Repository configuration
One or more custom 'site' web applications that deliver content using the HST delivery framework, including page templates and components
Custom integrations and extensions as required

A Bloomreach Content implementation project is developed, maintained, and supported by the Bloomreach customer or an approved partner.

Production Instance

A production instance is an implementation project deployed to a live, production server environment.

A production instance contains:

Content such as documents, images, and assets
User accounts, groups, security domains, and permissions
Channel configuration, including page template and component configurations
Visitor data collected by the Relevance Module

End users—including authors, editors, and administrators—manage the production instance.

Support for a production instance is determined by agreements between Bloomreach, the partner, and/or the customer, and depends on whether the instance is deployed on-premise or on Bloomreach Cloud.