Products

Five management systems on one shared platform

Each product has its own catalogue of registers, roles, navigation and internal chat. They share tenancy, licensing, payments, messaging, storage and presentation, so an operator manages one estate instead of five disconnected installations.

Advertisement
86 registers

School management

Admissions, CBC assessment, fees, HR and payroll, library, hostel, transport, communication and parent self-service.

94 registers

Healthcare management

Front desk, clinical care, diagnostics, pharmacy, wards, insurance claims, revenue cycle and hospital workforce.

32 registers

ISP hotspot billing

Subscribers, packages, invoices, vouchers, sessions, routers, coverage, support and revenue reporting.

40 registers

SACCO / microfinance

Membership, shares, savings, credit, accounting, banking, insurance and digital banking registers.

43 registers

Community / society

Residents and tenancies, gate security, community feed and chat, facility bookings, helpdesk, finance and CMS.

Shared core

Platform services

Tenant isolation, licensing, payments and payouts, SMTP and SMS credits, storage quotas, exports and presentation.

Specialist services

Focused deployments on the same platform

Where a team needs a narrower scope, these service lines run on the same tenancy, licensing, payments and messaging core.

Education

Education and learning services

Admissions, fees, attendance, live classes, payroll, library, transport and parent portals for academies and learning centres.

Clinical

Healthcare services

Patient records, clinical notes, diagnostics, pharmacy, billing and insurance claims for clinics and hospitals.

Pharmacy

Pharmaceutical services

Medicine catalogue, batch and expiry control, purchases, prescriptions, dispensing and stock movements.

Ministry

Religious and ministry services

Membership, attendance, giving, events and finance for churches, ministries and religious institutes.

Distinct access, by design

  • Every request is checked against the member's product role, not just the menu.
  • Self-service roles (parent, student, patient, member, subscriber) cannot open staff chat.
  • Workspaces are isolated by tenant; cross-tenant reads fail closed.
  • Sensitive actions are written to the hash-chained audit log.

One chat per product

  • Staff coordinate in tenant-scoped threads inside their own product.
  • Threads never cross workspaces or products.
  • Platform operators can switch chat off for a product without a deployment.
  • Messages and thread changes are audited.

Not sure which product fits?

Open any demonstration, or talk to us about a workspace for your organisation.