PLATFORM ARCHITECTURE · FOR ENGINEERS

17 modules.
Every service inherits them all.

CAPSaaS is the composable backbone — 17 modules across 4 layers — that every service inherits. This page is the engineering reference. Customers don't see this; they see services.

The model

Three layers.
Strict separation.

Modules build services. Services run for tenants. Each layer has its own audience.

LAYER 1 17 Platform Modules CAPSAAS ENGINEERING
Composable building blocks. Auth, Tenancy, Storage, Notifications, Billing, Audit, and more. Maintained by CAPSaaS. Never tenant-visible.
↓ COMPOSED INTO
LAYER 2 Service Catalogue BUILT BY CAPSAAS · SOLD TO TENANTS
Business capabilities composed from modules. Schedule Management, Donations, Appointments, Case Management. Only CAPSaaS builds services.
↓ ACTIVATED FOR
LAYER 3 Tenant Application WHAT CUSTOMERS SEE
A working application provisioned by CAPSaaS, containing only the services activated for one tenant. Tenant-branded. Modules are invisible at this layer.
Layer 1 detail

The 17 modules
in detail.

Engineering reference. Module names, numbers, and configurations never appear in tenant-facing surfaces.

FOUNDATION Layer 1 Mandatory · everything else depends on these
01Auth & IdentityCORE
02Tenancy & WorkspacesCORE
03Secrets ManagementCORE
RUNTIME Layer 2 Where the work happens
04Orchestration & WorkflowCORE
05Storage & DataFLEX
06Files & MediaFLEX
07Search & IndexingCORE
15AI & InferenceNEW
SURFACE Layer 3 Talking to the outside world
08API Gateway & SDK LayerCORE
09Webhooks & EventsCORE
10NotificationsCORE
16Connectors & IntegrationsNEW
17Admin Console & CLINEW
GOVERNANCE Layer 4 Operations, control, compliance
11ObservabilityCORE
12Audit, Compliance & Data ResidencyCORE
13Billing & MeteringCORE
14Feature Flags & ConfigCORE
i
CORE — every service inherits, no opt-out.  FLEX — customer can bring their own (same contracts).  NEW — recently added, versioning policy applies for 6 months.