Private preview — no active form submission or frontend analytics.
RedHover product family
RedHover assigns four business responsibilities to four clear product roles. Launch covers capabilities for digital presence, Relay for communication, Command for customer relationships and sales workflows, and Engage for digital collaboration. Each product can be evaluated independently; RedHover OS explains the intended connections.
The product roles describe evidenced scope and the target model. They prove neither general availability nor an active integration or mandatory bundle.
Four independent roles
Digital presence
Create, manage, and publish with control
Pages, content, media, forms, localization, SEO, and publishing tools in one clear product role.
No active publishing, form delivery, or customer domain is claimed.
Choose LaunchBusiness communication
Organize communication and bounded workflows
Email, templates, bounded campaign and communication workflows, and communication records.
No active delivery or accepted provider connection is claimed.
Choose RelayCustomer and sales work
Organize relationships, tasks, and business workflows
Companies, contacts, leads, opportunities, tasks, and sales stages in a governed product context.
No active CRM runtime or production connector is claimed.
Choose CommandDigital collaboration
Shape collaboration in branded Spaces
Dedicated digital Spaces with content, files, plans, forms, external access, and conversations.
No production availability or capacity allowance is claimed.
Choose EngageGuided orientation
Filter the four product roles by the responsibility you want to understand first. This does not produce an automatic recommendation or score.
All four product roles are shown.
Digital presence
Pages, content, media, forms, and controlled publishing.
No active publishing is claimed.
Business communication
Email, templates, and bounded campaign and communication workflows.
No active delivery is claimed.
Customer and sales work
Customer relationships, tasks, sales stages, and connected workflows.
No active CRM runtime is claimed.
Digital collaboration
Branded Spaces for content, files, plans, forms, and conversation.
No production availability is claimed.
| Criterion | RedHover LaunchProduct | RedHover RelayProduct | RedHover CommandProduct | RedHover EngageProduct |
|---|---|---|---|---|
| Primary responsibility | Digital presence | Business communication | Customer and sales work | Digital collaboration |
| Evidenced product scope | Pages, content, media, forms, and publishing | Email, templates, communication workflows, and records | Companies, contacts, leads, opportunities, tasks, and stages | Spaces, content, files, plans, forms, and conversations |
| Role in the target model | Passes eligible business context to Command | Supports Command when communication is required | Owns the customer and business process | Provides the external Space when configured |
| Not claimed | Active publishing or form delivery | Active delivery or provider operation | Active CRM runtime or production connector | Production availability or capacity allowance |
This comparison describes product responsibilities and intended connections. It is not an availability or runtime commitment.
The guided view changes only the presentation of this evidenced comparison. It does not assess suitability or send data.
Shared foundations
The RedHover platform describes shared architecture and governance principles behind the independent products.
It is not selectable, not a separate price line, and not proof of an active shared runtime.
Explore platform foundationsConnected target model
RedHover OS describes the intended interplay of Launch, Command, Relay, and Engage through clear handoffs.
The target model is not proof of an active cross-product runtime or monolith.
Explore RedHover OS