EO Global, System Architecture
Three layers, top to bottom. Chapter interfaces (Hivebrite for all 220 chapters, HubSpot Brands for ~60 power users) sit on top of a custom middleware control plane that reads and writes to both data stores, with an API bridge syncing HubSpot deals to Altai.
EO Global, System Architecture Overview
Upper Layer, Chapter User Interfaces
Hivebrite
All 220 Chapters
Chapter Managers and Member Leaders interact with chapter operations, membership data, and community tools through Hivebrite.
Standard, All Chapters
HubSpot Brands
~60 Power User Chapters
Advanced chapters get dedicated HubSpot Brands for marketing, communications, and deeper process management.
- 1 Core License
- 1 Sales License
- 1 Marketing License
EO Global Allocation, ~60 of 220
Surfaced through Middleware
Middleware Layer, Custom Code
{ }
Admin Control Plane
Custom-built middleware that allows authorized admins to read and write data directly into either system. Acts as the integration and management layer between HubSpot and Altai.
Update HubSpot
Update Altai
Read / Write Access
Bottom Layer, Data Stores
HubSpot
Lead to Deal Close
- Member Acquisition
- Strategic Alliance Partner Acquisition
- Non-Member Programs
API
Deal close triggers sync to Altai
Altai
Post-Close Operations
- Member records
- Chapter management
- Post-deal lifecycle