Built on isolation, not exceptions.
Security isn't a layer bolted on top of Jigi — tenant isolation and access control are part of the core architecture every module is built against.
Security
Tenant isolation
Every request is scoped to a tenant at the platform level. Data, permissions, and configuration for one organisation are never visible to another, even on shared infrastructure.
Encryption everywhere
Traffic is encrypted in transit via TLS. Data at rest — including documents and database storage — is encrypted using industry-standard algorithms.
Authentication & access control
Token-based authentication with short-lived credentials, paired with granular, action-level permissions — a user only sees what their role explicitly grants.
Audit logging
Sensitive actions — approvals, role changes, license operations — are recorded to an immutable audit trail available to workspace administrators.
On-premise option
Organisations with strict data-residency requirements can run Jigi entirely within their own infrastructure, activated through a signed, offline-verifiable license.
Responsible disclosure
We welcome reports from security researchers. Valid reports are triaged promptly and we will keep you informed as a fix is developed and shipped.
Found a vulnerability?
Report it to security@jigi.io. Please include enough detail to reproduce the issue and avoid accessing data beyond what's needed to demonstrate it — we'll take it from there.