You hold client money. Your software should act like it.
ConnetikIQ is multi-tenant by architecture, not by convention. Isolation, encryption and least-privilege access are built into the foundation — because in broking, trust is the product.
Your data lives in its own house
Many multi-tenant systems put every customer's rows in the same tables, separated only by a tenant ID — one missed filter from a leak. ConnetikIQ gives every brokerage its own database schema. Isolation is enforced by the database, not by remembering to add a WHERE clause.
- Separate schema per brokerage
- No shared tenant-id columns to leak through
- Isolation enforced at the database layer
Security built into the foundation
Not a checklist bolted on at the end — these are properties of how the platform is built.
Schema-per-tenant isolation
Each brokerage's data lives in its own PostgreSQL schema — physically separated, not filtered by a shared tenant column.
JWT RS256 authentication
Signed tokens delivered in httpOnly cookies, so credentials are never exposed to client-side scripts.
Granular permissions
Role-based access control down to the individual action — finance, claims and admin gated independently.
Account protection
Account lockout on repeated failures and secure password-reset flows guard against credential attacks.
Auditable by design
Sensitive actions — like journal reversals and period locks — are recorded with who, what and when.
Self-service M365 connect
Microsoft 365 calendar and email connect via Graph with per-user consent — no broad admin access required.
Want the security details?
We're happy to walk your team or your IT through how ConnetikIQ isolates, encrypts and audits your brokerage's data.