RPI v6.x vs. RPI v7.x feature comparison

Overview

There are some notable differences between Redpoint Interaction (RPI) v6.x and v7.x, including in the areas of architecture and deployment models, available connectors, and features. This topic provides an overview of these differences.

Architecture and deployment

One of the most important differences between RPI v6.x and v7.x is the overall architecture and deployment models.

RPI v6 uses traditional deployment models, such as Windows/Linux servers or virtual machines (VMs). Refer to the following resources for additional information:
- Admin: Introduction (and sub-topics): provides high-level information about RPI v6 architecture and components.
- Admin: Installation: provides information about how to prepare for installing RPI v6.
RPI v7 is the first cloud-native version, fully re-architected around Kubernetes and containers. This approach eliminates the need to provision or manage VMs or multiple servers for high availability; instead, it leverages container orchestration for scalability, resilience, and cost efficiency. Refer to the following resources for additional information:
- Admin: Deploying RPI: how to deploy RPI v7.
- Upgrade to RPI v7.x: the preparation and steps to take to upgrade from RPI v6.x to RPI v7.x; includes details about resilience and usability improvements to RPI v7.x.
- RPI GitHub repo: comprehensive information about deploying RPI v7.x in Kubernetes using Helm.

Connectors

There are some significant differences between the connectors provided in RPI v6.x and those provided in RPI v7.x. Refer to the following resources for specific information:

Connector read/write: delineates which connectors are available for RPI v6.x and RPI v7.x in one place.
RPI v7.x Supported connectors: details the connectors supported in RPI v7.x.
RPI v6.x Supported connectors: details the connectors supported in RPI v6.x.

Features

The feature set in RPI v7.x vs. RPI v6.x has primarily been additive; that is, what is in v7.x enhances existing v6.x functionality. Core workflows, audience designer, offer designer, and Realtime decisions remain largely unchanged.

Features added or enhanced in RPI v7.x

Here are some highlights:

AI capabilities: AI-assisted Basic selection rules and AI content generation are new productivity tools that can speed up segmentation and content creation.
Multi-language workflows: New Localization Asset improves governance and simplifies multilingual campaigns.
Operational enhancements: Telemetry, diagnostics, prioritization, and AI content tools can improve productivity, governance, and operational visibility.

The following table provides more granular details about the changes from RPI v6.x to RPI v7.x:

Functional area	v6.x (baseline)	Key enhancements in v7.x
Selection / segmentation rules	Standard selection rules, Basic selection rules, and NoSQL selection rules.	Introduction of an AI-chatbot style interface in Basic Selection Rules to help generate criteria. This may reduce manual creation effort. Support for System Variables at cluster‐level to be used in Standard/Basic selection rules and in content, providing more global manageability. Warning when a compare to list criterion contains an excessive number of values in Interaction Designer, which may assist with helps governance and performance.
Assets & content (Text / HTML / Smart Assets, localization)	Support for text, HTML, image, web-form assets; localization via “variants” in assets.	New Localization Asset type allows a set of strings for multi-lingual translations, which may streamline translations; the older method (variants in text/HTML) is deprecated. Content Generation Tools allow you to use AI tools (ChatGPT/Writer) in an email offer, landing page, and text/HTML asset designers, which streamline copywriting processes.
Interaction / workflow designer	Core workflow trigger types, activities, etc.	These enhancements bring more control and sophistication to workflow orchestration, which is especially helpful if you have complex multi‐step campaigns: New Prioritization tab for all interaction workflow triggers allows you to set the priority of workflow activities, override max queued time prior to execution, and mark an “urgent from” date/time. In the Interaction Designer, for a recurring trigger you can now use a "Check constraint(s) for" property. When an interactive activity follows another interactive activity, there is a new checkbox “Allow extra time for upstream interactive delays”.
Data import / ad‐hoc data loading	Primary reliance on other mechanisms (RPDM, etc.) for data ingestion; limited ad-hoc file load.	Introduction of Data Import Designer allows you to load files on an ad hoc basis into the RPI data warehouse for tactical use (e.g., short list of customers for a one-off email).
Monitoring / telemetry / operational visibility	Standard logging/monitoring but less formalized telemetry reporting in product UI.	For operations/DevOps teams, these features improve visibility and troubleshooting/diagnostic capabilities in v7.x. If you run large scale or mission-critical campaigns where you need monitoring, this is beneficial. A new Telemetry tab in the Operations interface allows you to generate an Excel Telemetry Report (includes audit metrics, active triggers, database queries, etc.). A Diagnostics Mode tab in Operations (initiate diagnostics session collate logs etc.).
Realtime / audience / Realtime decisions	Core Realtime capabilities (visitor profiles, Realtime decisions, etc.).	Enhancements such as copy/paste in the Specify Values dialog for web events in a Realtime decision. Localized content and system variables apply in Realtime contexts.
Tenant / configuration management (functional)	Tenant config and setup capabilities were present but fewer “template” features.	New Template Tenant Deployment feature: A new Tenant Template Export button to export a tenant’s configuration for reuse when creating a new tenant. If you manage many tenants (e.g., multi-brand, multi-region) this is a handy functional enhancement for configuration re‐use and consistent setups.
User / authentication enhancements (functional)	Support for basic authentication, LDAP/OpenID, etc. but less deep integration.	Deeper integration with Keycloak for user source: users can be created/managed in Keycloak and surfaced in RPI’s User configuration interface, which provides better user management for enterprise SSO environments.
Miscellaneous usability enhancements	v6 had baseline designer/user interface.	In Config > User Groups, ability to choose users for assignment to a user group from the group context. In the File System UI, ability to delete non-empty folders.

Features removed in RPI v7.x

Functional area	Migration notes
Data Project Designer (Data Intake)	Data Project Designer no longer exists in RPI v7.x. Use alternate methods (OAPI, Deployment API, Data Import Designer).
Server Workbench (UI/tool)	Administration and configuration tasks are now handled via Deployment API, Clients tab, or Helm chart.
Training Aids (“Build an Email”, “Send Emails”)	Training content removed; use external guides or updated docs for onboarding.
Legacy localization variants in assets	Migrate multi-language assets to the new Localization Asset approach.