Skip to Content
Aegis Platform

The shared operating foundation behind focused vertical brands.

Every Aegis vertical starts on the same foundation. The differences live in the domain logic on top.

Platform Capabilities 8 clusters active
3
Enterprise → Org → Tenant
7
Module clusters
1
Shared core
Core Infrastructure Active
Customer Operations Active
Communications Active
Documents & Content Active
Billing & Finance Active
Compliance & Analytics Active
Automation & Intelligence Active
Continuity & Lifecycle In design
Thesis

Sound business core. Vertical precision.

Aegis is the platform engine behind a portfolio of vertical brands. It is built around the conviction that every operating business needs the same disciplined foundation — customers, worklists, billing, communications, documents, forms, reporting, automation, permissions, and auditability — long before any industry-specific feature is meaningful.

From that foundation, Aegis adds the domain logic that makes healthcare, wine commerce, mortgage operations, and other regulated industries work the way they actually work. The platform compounds; the verticals stay focused.

Multi-entity structure

Enterprise → Organization → Tenant

Multi-location, multi-program, and multi-payer organizations modeled correctly from day one. BillingIdentity is attachable at Enterprise, Organization, Tenant, or Channel level — each node carries its own TIN and NPI. The correct shape for healthcare, wine, mortgage, and any regulated multi-entity operating model.

Permissions, audit events, and canon boundaries flow down the same hierarchy. Every action is tenant-scoped; every role is enterprise-aware.

Enterprise
Organization
Tenant
Role / Permission
Audit Event
Canon Boundary

Platform capabilities

The shared core every Aegis vertical inherits.

Core Infrastructure

Multi-tenant isolation

Global query filters; per-tenant data scoping enforced at the query layer, not application logic.

Enterprise → Organization → Tenant hierarchy

Three-tier hierarchy with polymorphic BillingIdentity. TIN and NPI at every relevant node.

Provisioning / control-plane

Tenant signup, offering descriptors, and self-service onboarding. 9-table control plane.

Bridge Enterprise Portal

Operator cockpit for enterprise and platform admins. EnterpriseAdmin role. Module-contributed /admin workspace.

Storage (IBlobStore + MinIO)

Binary artifact storage. FileSystem and MinIO provider adapters. Pluggable per deployment.

Event Bus (pgmq)

Async publisher/subscriber with inbox dedup. Production publishers across clinical, billing, and CRM events.

Customer Operations

CRM

Contacts, leads, organizations, deals, opportunities, and notes. Full lifecycle from lead to customer.

Relationship Analytics

Contact gap detection, touchpoint summary, response time. IRelationshipAnalyticsReader on TimescaleDB.

Communications

Comms.Fax (eFax)

Healthcare-grade fax: inbound routing, DID→Contact match, AI-assisted clinical extraction, FHIR extraction seam.

Sentinel Chat

HIPAA-grade live chat. Postgres 17 + TimescaleDB + pgmq + Caddy.

SMS + Email

Notification channels. No-PHI default posture. Consent and audit baked into the model.

Documents & Content

CMS + Forms

Full-chain CMS. Structured intake forms, submissions, and document lifecycle.

DocRadar

Document intelligence: pentagon scoring, extraction, canon comparison, exception routing, and provenance chain.

Billing & Finance

Billing & Ledger

Subscriptions, invoices, payments. Double-entry general ledger for regulated-industry auditability.

PayDoc EDI & RCM

Claim-to-cash: 837P, 835 ERA, 999/277CA, claim scrubber, payer routing, ERA ingestion, remittance posting, denial management, GL reconciliation.

PayDoc Credentialing

Payer enrollment, license status, and credential expiry tracking with renewal alerts.

Aegis Clearinghouse

Production EDI clearinghouse. Not a third-party relay.

Compliance & Analytics

Sentinel Analytics

HIPAA analytics pipeline. TimescaleDB hypertable. IRelationshipAnalyticsReader.

Permissions & Audit

Role-aware access boundaries. Change history on every action. Consent controls per tenant, per workflow, per role.

Public Intel

Governed regulatory canon: ReferenceSource, Obligation, Binding, ReviewTask, CanonPack. Wine and Healthcare canon packs.

Automation & Intelligence

Automation / IFTTT engine

Trigger → condition → action across all platform events. Cockpit/worklist UI. Fires on CRM, billing, fax, and domain events.

Aegis.Web.Design RCL

MD3 token layer. Component library. Themes per brand. Shared across Bridge, platform workspaces, and vertical UIs.

Continuity & Lifecycle

Retain — Continuity engine In design

Cross-vertical relationship lifecycle: recurring relationships, memberships, renewals, reactivation, lifecycle state, reimbursement-support workflows, and retention analytics. Retain detail →

Platform-native workflow primitives

Every regulated workflow follows the same spine. The platform models it once; verticals inherit the shape and add domain steps.

Tenant isolation
Permissions & audit
Human approval
Governed canon
Claim-to-cash visibility
Document handoffs

Building a vertical that fits this pattern?

Aegis is designed for industries where workflow, compliance, money, communication, and data have to move together.