Skip to content
Apex Cloud Technologies logo

SaaS · Product Engineering

What SaaS architecture Apex refuses to postpone

Tenancy, roles, and the admin an operator needs are cheaper to design before the first customer than after the tenth.

Apex Engineering · May 7, 2026

Apex runs DotlyMaps, DotlyGuard, LeadsFizz, and Zomani. The mistakes that hurt are the ones that looked small before anyone paid: a tenant id added later, an admin screen that is a database viewer, a role model that is only “user” and “admin”.

Tenancy is a data decision. Every customer-owned record needs an owner, and queries need to enforce it. Retrofitting that onto a single-tenant schema is how launches slip.

Roles follow the real organization. A sales manager, a finance reviewer, and a customer admin are not the same person. If the first release pretends they are, the second release rewrites authorization.

The operator needs a surface too. Impersonation, plan changes, and a way to see why a job failed are product features. They are not “internal tools we will add if there is time”.

Client SaaS engagements at Apex start with those three. The interface can be narrow. The model should not be.