You can use one Ackaia ID as the identity layer across participating Ackaia products.
This gives the ecosystem a consistent account and authentication foundation without requiring each product to create a separate identity for the same person.
Depending on the product and current architecture, Ackaia ID can provide continuity for information such as:
your account identifier;
authentication state;
basic account identity information;
account and security status;
applicable subscriptions or entitlements;
session and authorization context.
Using one identity does not mean that every product shares all product data.
Product-specific information can remain within the product boundary, including:
files and folders;
product-specific settings;
product-specific metadata;
organization or workspace information;
product permissions;
product-specific cryptographic material.
No.
Ackaia ID can provide a single sign-on foundation, but access to a particular service may still require:
a valid entitlement;
a subscription;
specific permissions;
organization membership;
regional availability;
additional security verification;
a valid product-specific state.
A valid identity session should not be treated as unlimited authority across the entire ecosystem.
When you use CipherDriveâ„¢, Ackaia ID provides the account and authentication boundary.
CipherDrive can receive the account and entitlement information it needs, such as an account identifier, account status, subscription status, and applicable security settings.
CipherDrive still maintains its own encrypted-storage responsibilities. An Ackaia ID session is not itself the plaintext CipherDrive master key or file key.
Ackaia One is the subscription layer for applicable consumer products.
This means the three concepts have different roles:
Ackaia ID: who you are to the ecosystem and how you authenticate;
Ackaia One: which subscription or consumer entitlements apply;
the product: the service you are actually using.
Separating identity, subscriptions, and product responsibilities makes it easier for Ackaia to add products without turning the ecosystem into one large application or duplicating identity infrastructure.
It also makes security boundaries clearer: identity can be shared while product-specific access remains scoped.
One Ackaia ID gives you one identity across the ecosystem—not one unrestricted permission set across every product.