Ackaia separates identity, subscriptions, storage, and cryptography into distinct layers. Understanding those layers makes it easier to know which part of the ecosystem is responsible for your account, your plan, and your encrypted files.
Ackaia Corp. is the company that builds and operates the ecosystem.
Ackaia ID is the identity and authentication layer.
Ackaia One is the consumer subscription and entitlement layer.
CipherDrive™ is the encrypted file-drive product.
Cryptographic Engine™ is Ackaia's source-available client-side cryptographic core behind its storage architecture.
Ackaia ID provides the shared account and authentication boundary for participating Ackaia products. It handles account access and helps services make authorization and entitlement decisions.
When you open CipherDrive, the storage product can receive the account information it needs from Ackaia ID, such as your account identifier, name or display name, email address, account or subscription status, plan information, and relevant security settings.
Ackaia ID does not replace CipherDrive's file-encryption layer. Successfully signing in to your Ackaia ID does not mean Ackaia ID has the keys required to decrypt your vault.
Ackaia One is the subscription layer for Ackaia's consumer products. It represents the billing relationship, plan, storage entitlement, and the access model that can apply across Ackaia products.
For CipherDrive, Ackaia One can determine the product access, storage allowance, transfer capacity, or benefits associated with your subscription. It is not the file-storage application itself.
CipherDrive is the dedicated storage product. Its job is to provide the encrypted drive experience: files and folders, uploads and downloads, supported previews, sharing, storage accounting, transfer accounting, and the security boundaries specific to private file storage.
Supported file content is encrypted in the client before ordinary encrypted storage. Ackaia's infrastructure stores the encrypted objects, encrypted key material, and operational metadata required to run the service.
The Cryptographic Engine is the source-available client-side encryption core behind Ackaia's storage architecture. Its purpose is to make important parts of the cryptographic behavior inspectable rather than requiring users to rely only on a marketing promise.
The engine and the CipherDrive security documentation describe how client-side encryption, per-file keys, key wrapping, authenticated encryption, and related cryptographic operations protect supported stored content.
A simplified CipherDrive access flow looks like this:
You authenticate with Ackaia ID.
Your account and Ackaia One entitlement determine whether and how you can access CipherDrive.
CipherDrive opens your encrypted-drive experience and coordinates storage, sharing, limits, and security controls.
Your client uses the required local cryptographic material and Ackaia's cryptographic implementation to encrypt or decrypt supported content.
Ackaia's servers coordinate the service without ordinarily receiving the keys needed to decrypt the stored plaintext file content.
The separation creates clearer security responsibilities:
an identity service should authenticate and authorize accounts without becoming the storage product;
a subscription should define entitlements without becoming the application that holds your files;
a storage product should document its own privacy, encryption, metadata, sharing, and recovery boundaries;
cryptographic behavior should be independently inspectable where Ackaia makes it source-available.
This also means a problem in one layer does not always mean the same thing in another. For example, recovering an Ackaia ID account can restore account authentication while still leaving an encrypted vault inaccessible if its required cryptographic secret has been lost.
CipherDrive is the drive. Ackaia One is the subscription. Ackaia ID is the identity layer. Ackaia Corp. is the company building the ecosystem.