Security
A platform posture designed for real operational control.
Rikki is built for teams that care about authentication, permissions, tenant separation, auditability, and reliable hosting posture as part of a credible quality system.
Authentication & MFA
Account sign-in supports secure authentication flows and multi-factor verification for teams that need stronger access control.
Permissions
Scoped permissions are designed around organizations, companies, sites, departments, roles, and ownership boundaries.
Data isolation
Rikki is designed for tenant-aware separation so each organization works inside its own governed operating context.
Partner isolation
Partner-led delivery models preserve client boundaries while still supporting central partner administration and transfer-ready ownership.
AWS hosting
The platform is hosted on AWS with infrastructure choices designed for resilience, access control, and operational reliability.
Backups & recovery
Operational backups and recovery planning help reduce the risk of data loss and support service continuity.
Encryption
Rikki is designed to protect customer data in transit and at rest as part of its baseline security posture.
Audit trails
Controlled actions, ownership changes, and workflow activity are structured to support clearer auditability over time.
Compliance posture
The product is built for regulated and audit-heavy teams that need credible operational controls, not just storage.
Architecture diagram
How the security model aligns with the operating structure.
Rikki’s security posture is strongest when the tenant model, organization structure, permissions, and reporting boundaries all reinforce each other.
What strong platform trust means in practice.