Built as a platform, not a desktop product in the cloud.
Five technical decisions that explain how cifraHQ Enterprise scales, complies and integrates.
Five decisions that define the platform
Database per tenant
Physical isolation on Azure SQL elastic pools. Auditable, backable and restorable per tenant.
REST-first with OpenAPI
Auto-save on every screen, concurrency control via RowVersion, webhooks.
SOC 2 from day one
Dual audit trail, DENY UPDATE/DELETE on audit events, Key Vault for secrets.
Three layers in one diagram
The license server governs access. The master catalog (CiferaHQ_master) stores global metadata in its own
elastic pool with geo-replication. Each customer has their own SQL database — physical isolation, not logical.
Multi-currency and period close, solved at the root
Original currency preserved
Every GL line stores <code>OriginalCurrency</code> and <code>OriginalAmount</code>. Daily FOREX auto-update.
Six-state period machine
<code>Unlocked</code> → asymmetric locks → <code>Locked</code> → <code>Closed</code>. Audited immutability.
P4 Warehouse as boundary
Explicit warehouse frontier. cifraHQ owns the what; P4W owns the where.
Talk it over with an engineer
45-minute technical demos on isolation, API and compliance.