One organization. One protected space. Every business app.
Rakon Cloud is the platform layer between your team and the applications it uses. It manages organization identity, members, roles, access and plans so Flow, DMS, People, Books and future apps can operate within the same tenant.
Cloud is not another business app — it connects them.
Applications solve individual business processes. Rakon Cloud solves what they share so every new tool does not require another set of accounts, teams, permissions and organization context.
One tenant
Your company exists as one organization with its own identity and isolated data space.
One team and access model
Owners and administrators manage members, roles and which applications each user may open.
Apps as needed
Activate only the applications and modules you need without changing tenant or rebuilding the team.
Controlled connection
An app receives only the verified tenant, user, role and allowed capabilities it needs to operate.
Organization data is not merely tagged with a tenant ID — the tenant has a separate database.
Rakon Cloud applies several layers of control to keep a request within the organization the user belongs to.
No information system can responsibly promise absolute security. Rakon Cloud reduces risk through layered isolation, access controls and short-lived context exchange between applications.
Membership check
Every protected request first verifies that the signed-in user actually belongs to the active tenant.
Separate organization database
When an organization is created, the platform assigns its own tenant database, separate from other organizations.
Dedicated database account
Each tenant receives a database account restricted to its database only. Credentials are stored encrypted.
Application access check
Company membership does not unlock everything: the app, role, plan, modules and explicit user permissions are checked.
Security is verified at each boundary, not just at sign-in.
MFA for business apps
Users must enable TOTP multi-factor authentication and pass the sign-in challenge before opening applications.
Controlled sessions
Idle and over-age sessions expire; signing out invalidates the session and regenerates its protection token.
One-time application launch
Cloud issues a short-lived token bound to one user, tenant and application. It is consumed during context exchange.
Minimal context
The app receives only identity, tenant, role, allowed apps, plan and modules required for authorized work.
Protected cookies and requests
Production uses HTTPS, HttpOnly/SameSite session cookies and CSRF protection for data-changing requests.
Critical event records
Provisioning, denied access, plan changes and other sensitive operations create structured records for operational review.
A shared tenant does not mean uncontrolled data sharing.
The platform shares controlled context
- Organization identity
- User and membership
- Role and application access
- Plan, modules and allowed capabilities
- Minimum data needed for secure launch
The platform does not share automatically
- Complete business data from one app with another
- Documents, contacts or HR records without a defined need
- App access merely because a user belongs to the organization
- Another tenant’s data or credentials
When two applications need to collaborate, the integration must explicitly define which data is exchanged, for what purpose and under which permissions.
Today’s and future applications enter the same organization framework.
A new application does not need to rebuild company registration, members, roles, billing or tenant identity. It connects to the platform contract and inherits verified context while retaining its functions and data inside a clearly defined domain.
- 01
Add an application
The organization activates the application or module it needs.
- 02
Choose who gets access
An owner or administrator assigns it to the appropriate members.
- 03
Cloud passes verified context
The app receives the tenant, user, role and allowed capabilities.
- 04
The team stays in one workspace
No new organization, duplicate members or parallel access administration.
A company can start with Flow and add applications as it grows.
The tenant, team and security framework remain the same. Only the set of applications the organization uses changes.