1. Introduction

Companies must be where their customers are. Simply providing information on their own company website is therefore no longer sufficient. Instead, customers have to be addressed through various channels, the number of which is growing at an ever faster rate. The ability to distribute content flexibly is a basic requirement for this.

Content as a Service (hereafter referred to as CaaS) offers companies the agility necessary for this customer communication. It enables the provision of content fragments and has an interface for their retrieval. Without any additional implementation effort, data can thus be reused indefinitely. Publishing to a targeted channel is no longer necessary.

In accordance with the best-of-breed philosophy, the design and composition of the presented contents are thus completely detached from FirstSpirit. This increases independence, flexibility and speed in project implementation.

2. Architecture

The functionality of CaaS is realized by an architecture of different components.

These components are:

caas architecture
Figure 1. Architecture

The interaction of the components follows the following scheme:

  • The creation and editing of editorial content takes place FirstSpirit-sided. The content is provided as part of a generation and all relevant data is transferred from the FirstSpirit Server to the CaaS platform.

  • The CaaS platform receives this data and updates its internal data model using the information contained in it. The data is persisted in the repository.

  • The customer’s end application requests the stored information from the CaaS platform when required. The query therefore follows the pull principle rather than the push principle.

  • To access the data in the repository, the CaaS platform provides a REST Interface. The REST Interface is not directly connected to the network, but only accessible via the Security Proxy. The Security Proxy is used for authentication and authorization of requests to the REST Interface.

  • The CaaS Admin Interface is to be seen detached from the other components. It is used to manage the project data transferred to CaaS platform and offers a simple, web-based administration interface for this purpose. This also accesses the information stored in CaaS via the REST Interface.

The communication between the FirstSpirit Server and CaaS is done via HTTP(S).

3. Components

This CaaS release in the version 2020-07-13 contains the following technical versions of the components:

Table 1. technical versions of the components
Component Version

CaaS platform


CaaS module


Further information is available in separate documentation for each component. These cover topics such as installation, operation, and usage, as well as all information regarding component updates, especially release notes and migration guides.

CaaS is a product of e-Spirit AG, Dortmund, Germany.

Only the licence agreed with e-Spirit AG applies to the user.

Details of any third-party software products used that are not produced by e-Spirit AG, their own licences and, where applicable, update information, can be found in the file 'THIRD-PARTY.txt', which is supplied with the relevant CaaS component.

5. Help

The Technical Support of the e-Spirit AG provides expert technical support covering any topic related to the FirstSpiritâ„¢ product. You can get and find more help concerning relevant topics in our community.

6. Disclaimer

This document is provided for information purposes only. e-Spirit may change the contents hereof without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. e-Spirit specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. The technologies, functionality, services, and processes described herein are subject to change without notice.