Pricing

XperienCentral supports the setting up of a staging infrastructure for creating code and/or content, also known as a DTAP-pipeline. DTAP represents the four main stages: Development, Testing, Acceptance and Production. If desired, an XperienCentral environment can be set up for some or all of these phases in the development process in order to stage new custom code and/or content before it is published on a “live” website or web app. For more details on how to determine your staging needs, get in touch with our sales team.

For example: in a staging environment with 3 environments (Development, Testing and Production), new code or custom plugins are developed and built in the Development environment. The live website hosted by the Production environment is not changed and therefore remains stable during the Development phase. When the new code and/or content is built and ready, it moves on to the next stage - Testing. This means it is migrated from Development environment to the Testing environment. Here, the developers and application managers or business owners can test the new functionality built by the developers. If approved, it is then rolled out to the Production environment. Hence, it “goes live”.

Instances are for scaling and redundancy. An instance is a combination of a valid XperienCentral software license and the hosted server on which it is installed.

Every XperienCentral environment consists of one (or more) instance(s). Because an instance has a specific capacity for handling traffic, receiving a lot of visitors, building many advanced personalizations and/or organizing large teams of content, editors may need your environment(s) to be scaled up. Redundancy may also be a reason to scale up. In a scaled-up scenario, the given environment (or multiple environments if it’s a staging infrastructure) are scaled-up and the one instance is connected to additional instances and automatic load balancing. The combination of these connected instances now functions as one environment but with a larger, redundant capacity and all traffic to and from the environment is evenly distributed across the total number of instances. For more details on how to determine your scaling needs, get in touch with our sales team.

When visiting a website powered by XperienCentral, data is transferred between a visitor’s browser and the XperienCentral server. This data is what we refer to as traffic.

Data consists of text, images, HTML, CSS, JavaScript, etc. The size of the transferred data is metered per month. This is what the Traffic parameters in our pricing model refer to - the combined total size of all data transferred per month  all environments in a staging infrastructure. Note that the data metered in all environments including the traffic generated by editors working in XperienCentral.

All content items in the XperienCentral Content Repository with a “published” status (or any equivalent status) are considered an accessible content item.

When creating, editing or managing content in XperienCentral, users create, edit or mange so-called content items, an item being one particular piece of content, such as a page, page section, an article or an image. These content items are stored centrally in XperienCentral’s Content Repository where users have access to advanced search and select tools, bulk actions and the means to open any content item in the in-context mode for in-context editing.

When a content item is first created, its status may be “Draft” or “In Progress”. Older items may have the status “Archived”. When any content item is set to “Published” (or any equivalent status as configured in the workflow management tool). it becomes visible on the website or inside a web app. In other words, it is now accessible, either via a URL (headful), via the content delivery API (headless) or both (hybrid). Note that custom content items, either coded or built using the Modular Content Tool are included. Note also that accessible content items are only counted on the Production environment: accessible content items in other environments in the staging infrastructure are excluded.

All form templates in Interactive Forms (IAF) on the Production environment with a “published” status (or an equivalent status) are considered to be an accessible form template.

When creating contact forms, building business logic or developing login capabilities for website visitors, XperienCentral users create so-called form templates. Each form template contains a specific configuration of fields, validations, logic and data integrations. In XperienCentral, all form templates are stored in the Interactive Forms (IAF) plugin where users have access to all the tools needed to build, configure and manage their form templates.

When a form template is first created, its status may be “Draft” or “In Progress”. Older form templates may have the status “Archived”. When any form template has the status “Published” (or any equivalent status as configured in the workflow management tool), it becomes visible, or at least usable for placement on the website or inside a web app. In other words, it is now accessible via a URL (headful), via the content delivery API (headless) or both (hybrid). Note that accessible content items are only counted on the Production environment – accessible content items in other environments in the staging infrastructure are excluded.

All user accounts with access to one (or more) environment(s) in an XperienCentral infrastructure are considered a user.

For secure access to the XperienCentral Workspace and development interfaces, every professional requiring access needs a user account. These user accounts, or users, can be created, configured and managed inside XperienCentral by the system administrator or in the integrated tools for Single Sign-On provided by your organization. All users with access to at least one environment in an XperienCentral deployment are considered a user as so defined in our pricing packages. Please note that visitors logging in to some kind of portal built with XperienCentral, such as a “myportal”, partner portal or webshop that does not access the XperienCentral Workspace or its development interfaces are excluded from the user count.

Additional instances can be added to any (new) environment to provide scaling, advanced staging and/or to create redundancy.

XperienCentral Starter, Professional, Business and Enterprise price packages all contain a default number of instances that can be set up in the environment(s). To introduce scaling, add redundancy and/or further expand the DTAP staging infrastructure, additional instances can be added as an Add-on to what is already included in the price package. For more details on how many environments and instances per environment you may need, get in touch with our sales team.

The instances for Production environments are configured and monitored to serve “live” websites 24 hours a day, 7 days a week, 365 days a year. 

The Development, Testing and Acceptance environments are meant for creating new code or content, testing that code and content and having it reviewed by the business owners. Most often this process of creating new functionality, testing it and having it reviewed, is done during office hours. Therefore, the demands for monitoring the Development, Testing and Acceptance environments, the connected instances, their up-time and our support for these instances are very different from what's needed for a Production environment.

For organizations with a (large) crew of editors and developers actively customizing the digital experience for their customers with XperienCentral, extended product support may be desirable. The same may apply for customers whose digital initiatives built on XperienCentral are essential for driving their business or for building their digital presence as a brand. For these organizations, the XperienCentral product support team offers Premium, Priority and Business Critical support packages on top of the basic support package which is free for all XperienCentral customers.

For more details on product support and what's included, check out the Add-ons section. Or, to get a quote; get in touch with our sales team.

XperienCentral Custom is available for all XperienCentral setups (Headful, Headless and Hybrid) and offers more traffic, items, or users than our Enterprise package as well as additional technical configurations. Do you want to learn more? Get in touch with our sales team and explore the possibilities.

XperienCentral is offered as a Paas/SaaS solution and is hosted at Amazon by default. This allows GX to offer a large set of advanced, yet standardized management features to all XperienCentral customers. However, there are more options available for organizations who wish to grow faster or want to meet specific requirements. Some examples of these are:

• extra high volumes of traffic, content items, form templates and/or users (above Enterprise)

• non-Amazon hosting such as on- premises, hosted in NL by GX or any other non-Amazon hosting provider

• custom instance configurations such as designated back-end/front-end configurations

• additional security measures such as VPN tunneling, secure data integrations, restricted instance access, etc.

• custom database configurations (redundancy setups, dedicated servers)

• custom maintenance windows

• dedicated clustered server configurations

• specific load balancing or scaling configurations (for example for launching campaigns)

• any other custom setup you may require.

Want to learn more about what we can do for you? Get in touch with our sales team and ask for XperienCentral Custom.