Built to connect growth, operations, and administration.
EbixEnterprise is designed as a connected platform with unified workflow across relationship management, agency operations, quoting, policy administration, claims, data, and AI. The architecture supports enterprise deployment, multi-tenant governance, and modern digital experiences.
Six foundational layers
The platform is organized into distinct layers that work together to deliver a complete enterprise experience.
Experience layer
Web application for brokers, agencies, operations, admins, and managers. Role-aware homepage, client cockpit, opportunity views, desk console, dashboards, admin settings. Embedded AI interaction points.
API gateway & edge layer
Authentication handoff, rate limiting, request routing, tenant resolution, API security, logging, versioning, external partner API exposure.
Business services layer
Domain-based services powering every operational capability across the platform, from tenant administration to AI orchestration.
Data layer
Primary relational database, search and indexing, document storage, analytics store, audit store, and caching layer for high-performance reads.
Integration & event layer
Synchronous APIs, asynchronous events, webhook framework, connector framework, mapping layer, retry and dead-letter handling.
Platform services layer
Identity provider, audit logging, notification service, file processing, AI model routing, localization, feature flags, observability, license metering.
How the layers connect
Every request flows through the same path: the experience layer calls the API gateway, the gateway routes into tenant-isolated business services, and those services are the only path to the data and integration layers. Platform services run cross-cutting alongside, and the AI orchestration path is governed end to end.
Multi-tenant by design
One codebase, tenant-level configuration, and strict data isolation. Every deployment shares the platform core while respecting the boundaries, rules, and behaviors unique to each tenant.
- Tenant-isolated data with strict boundary enforcement
- Shared services for identity, audit, AI, and notification
- API-first integration for every tenant boundary
- Configurable country and tenant behavior without code changes
- Scalable deployment from single-tenant to thousands
An API-first platform
Every capability in the platform is accessible through well-defined APIs, organized into four categories that serve different integration needs.
Internal application APIs
Service-to-service communication powering the platform experience layer and internal workflows.
External integration APIs
RESTful endpoints for carrier connectivity, third-party data exchange, and partner ecosystem integration.
Admin APIs
Tenant configuration, role management, feature toggling, and platform governance endpoints.
AI action APIs
Orchestration endpoints for AI model routing, prompt execution, and governed action confirmation.
Today’s EbixEnterprise architecture
EbixEnterprise runs the full health-benefits lifecycle, from an employee’s first enrollment election to the carrier’s general ledger. Two systems share one data backbone: a desktop administration suite used by carrier operations staff, and a web enrollment experience for members and external partners.
Derived from the current codebase · Prepared July 2026
Every request flows top to bottom: people and partner systems use the applications, the applications call a central business-services layer, and that layer is the only path to the data. External partners connect through the Partner API, and every partner call passes through a salt-based security-token handshake gate before it can reach the GR8 & General Ledger services or the Enrollment business layer.
Two systems on one platform
Both systems are built by the same team on a common .NET foundation and reconcile into the same general ledger.
Core administration: GR8
Windows desktop · WCF services · SQL Server
The system of record for carrier and TPA operations: group health policies, member eligibility, premium billing, ACH collection, general ledger, and nightly end-of-day reconciliation. Eligibility data feeds the in-house Luminx claim management system.
Used daily by internal operations teams. All business rules live in a central service layer, so the desktop application itself stays thin.
Self-service enrollment
Web application · REST partner API · SQL Server
The customer-facing side: employees and HR administrators elect and manage benefits through the web portal, while external benefit partners integrate through a documented REST API that reaches both enrollment and core-administration services under a salt-based token handshake.
Handles card payments through CyberSource, Chase, and third-party gateways, and runs nightly ACH payment batches that feed back into core administration.
LuminX: claim management
DB/C ISAM · AIM indexing · Indexed file system
LuminX uses a high-performance application database file system built on DB/C ISAM with AIM indexing. Rather than relying on a traditional relational database, the platform stores data in optimized indexed files designed for fast transaction processing, scalability, high reliability, and efficient retrieval of policy, claims, and eligibility information.
The technology stack in depth
A layer-by-layer view of the technologies behind both systems: policy administration on the Microsoft .NET stack, and LuminX claims on a DB/C engine with a C-ISAM balanced-tree database.
EbixEnterprise Admin
Financial, Policy & Premium Administration
- Application framework
- .NET Framework, C#
- Web application framework
- ASP.NET, ASP.NET MVC
- Service framework
- Windows Communication Foundation (WCF): stateless internal & external (SOAP “Smart”) services
- Data access / ORM
- Entity Framework (EDMX models), LINQ to SQL, LINQ to Objects
- Messaging / queuing
- Microsoft Message Queuing (MSMQ)
- Back-office UI
- Windows Forms smart client (Infragistics); auto-install & auto-update; client-side caching
- Web portal UI
- HTML5, CSS, JSON, Bootstrap; IE9–IE11, Chrome, Firefox, Safari
- Unified online portal
- Microsoft SharePoint (EbixEnterprise Online Portal)
- IDE / tooling
- Visual Studio; SQL Server Management Studio (SSMS)
- Source control / ALM
- Team Foundation Server (TFS): version control, branching, incident tracking, releases
- Document generation
- Aspose.Words for .NET: mail-merge (DOC, OOXML, RTF, HTML, PDF, XPS, TIFF, TXT)
- Transactional database
- Microsoft SQL Server
- Business intelligence database
- Oracle
- Operational reporting
- RDLC via SQL Server Reporting Services (SSRS): statements, trial balance, P&L, refund registers
- BI / analytical reporting
- IBM Cognos: high-volume batch-fed reports
- ETL / data integration
- Pervasive Data Integration: migrations, extracts, scheduled feeds (relational, EDI, flat file, XML)
- Import / export formats
- Excel, XML, ANSI X.12
EbixEnterprise Claims: LuminX
Claim adjudication & management
- Core programming language
- DB/C: base language of the claims engine
- Operating system
- Red Hat Linux (chosen for scalability & performance)
- Back-office UI
- .NET forms over core LX UI components: text-based or Windows-like interfaces
- Member web portal
- Java, HTML5, Bootstrap responsive design
- Single sign-on
- SAML 2.0 integration with the Policy Administration / Online Portal (SharePoint)
- Source control
- CVS: versioning, branching, configuration management
- Transactional database
- C-ISAM balanced-tree database (claims transactional information)
- Eligibility data source
- Direct connection to the Policy Administration MSSQL database (system of record)
- Business intelligence database
- Oracle Data Warehouse
- ETL / data integration
- Actian DataConnect ETL: custom extractions, transformations, regular feeds
How value flows through the platform
The five stages of the benefits lifecycle, and where each one runs.
Enroll
Employees elect benefits on the web portal; partners submit through the API.
Administer
Carrier staff manage policies, members, and eligibility in GR8.
Bill
Premiums are calculated, invoiced, and collected via ACH and card.
Account
Every transaction posts automatically to the general ledger.
Reconcile
Nightly end-of-day processing reconciles accounts and issues remittances.
Platform facts
See the architecture in action
Walk through the platform layers, integration model, and multi-tenant architecture with our team.