Architecture Patterns & Design Decisions
Behind every workflow in Zetta HRM is a set of architectural decisions designed to keep the platform reliable, scalable, secure, and operationally predictable as organizations grow.
These patterns ensure onboarding, payroll, attendance, billing, reporting, and governance workflows continue working consistently even under increasing operational complexity.
- Multi-tenancy — Every company operates inside its own isolated tenant boundary so employee, payroll, attendance, and billing data never leak across organizations
- Transactional provisioning — Company signup and onboarding run inside atomic transactions, ensuring incomplete provisioning never creates broken or partial system state
- Reliable email delivery — OTPs, invitations, and notifications are processed through retry-aware outbox queues to improve delivery reliability during temporary failures
- Billing failure handling — Failed subscription payments automatically retry with notifications before access restrictions are enforced, reducing accidental service interruptions
- Two-way Stripe sync — Billing state stays synchronized through both Stripe webhooks and direct API verification to prevent subscription inconsistencies
- Idempotency — Duplicate requests, repeated OTP submissions, and repeated webhook deliveries are handled safely without creating duplicate records or side effects
- RBAC with field-level scope — Access control is enforced across modules, actions, departments, and even individual fields to support granular organizational governance
- Comprehensive audit tracking — Critical system mutations preserve before-and-after snapshots with actor tracking for accountability, compliance, and historical traceability
- Reporting pipeline optimization — Aggregated reporting structures and precomputed fact tables improve analytics performance for operational and payroll reporting at scale