About SyncHive
What is SyncHive
SyncHive is a unified data platform that allows you to integrate cloud and on-premise applications, feed analytics, and build SyncHive-powered workflows, apps and agents.
Core Concepts
SyncHive’s design is built around key concepts that define how data is modeled, synchronized, and monitored within the platform.
Unified Data Store (UDS)
A shared data layer that stores and manages information from multiple external systems in a single, standardized form. It serves as the central repository for your organization’s unified business data, applying a canonical data model to maintain a consistent and authoritative view across the integrated environment.
Canonical Data Model
The structural blueprint that defines how data is represented within the Unified Data Store. It standardizes entities and relationships to reflect a common understanding of business concepts. Inbound data is transformed into this canonical form, and outbound data is translated back into each system’s native format, ensuring consistency and interoperability across all integrations.
Connector
Defines how SyncHive communicates with a specific external system (e.g., a CRM, ERP, or warehouse). It includes authentication, and the read/write semantics required to standardize inbound data and translate outbound updates. Connectors are designed for reuse, enabling many integrations to share the same connection logic.
Integration
A configured data flow that uses a particular connector to move a defined set of data. It specifies which entities are in scope, how they map to the canonical model, the direction and frequency of sync, and how changes are propagated. An integration represents a connection to one external system instance. A single connector may support multiple integrations, each configured with unique mappings, filters, and schedules.
Message
The atomic unit of data transfer within SyncHive. Messages contain structured payloads that represent records or changes moving between systems. They can be logged, tracked, inspected, and retried.
Event
A structured signal generated when data moves between systems or changes within them. SyncHive provides event-sourcing capabilities based on both data exchange events (reflecting sync outcomes) and data change events (reflecting modifications to the data itself), which users can subscribe to and use to trigger any downstream action or workflow.
Entity
The canonical representation of a real-world object or a business concept, conforming all directly related data about it across systems and contexts.
Shape
Defines the structure of a message for a specific data exchange use case. It includes selected properties from a root entity and any related entities needed for that context. Multiple shapes can be derived from a single entity to support different integration scenarios.