Zreta platform architecture

Zreta is the marketing, billing, and customer-portal layer for modular enterprise products. Live applications such as ChurchHub and CoreTrust run as separate products and connect through shared identity, payments, and support practices where configured.

Platform layers

┌─────────────────────────────────────────────┐
│  Zreta.com — storefront, CMS, docs, SEO     │
├─────────────────────────────────────────────┤
│  Shared services                            │
│  · Billing & invoices (GHS / Mobile Money)  │
│  · Customer portal & licenses               │
│  · Auth, MFA (staff), audit logs            │
│  · Support tickets & status                 │
├──────────────────┬──────────────────────────┤
│  ChurchHub       │  CoreTrust               │
│  (external app)  │  (external app)          │
│  Live            │  Live                    │
├──────────────────┴──────────────────────────┤
│  Roadmap products (ERP, School, Hospital…)  │
└─────────────────────────────────────────────┘

What lives on Zreta

Product catalog, pricing display, and honest Live vs Roadmap labels.
Checkout, subscriptions, invoices, and authenticated downloads.
Demo requests, contact forms, documentation, and system status.

What lives on product sites

ChurchHub application workflows (membership, giving, administration).
CoreTrust application workflows (loans, savings, collections).
Product-specific onboarding and day-to-day operations.