Feature list and edition comparison
Our Instant Cloud Database is available in different editions to better suit different business needs. The below comparison table shows the details of the selected features per edition.
| Stratus | Cumulus | Cirrus | Enterprise | |
|---|---|---|---|---|
| General | ||||
|
Number of users Users who only have administrative roles are not counted towards the total number of users. |
5 | 10 | 30 | as per the subscription |
|
Number of libraries Libraries are used to logically group entities and their branches, as well as manage default settings, layered security and cross-library lookups. |
2 | 5 | 10 | unlimited |
|
Number of entities and branches The total number of active entities and branches allowed. Archived entities and branches are not counted towards the total number of entities and branches. |
8 | 25 | 50 | unlimited |
| Entities | ||||
| Copy entities | ||||
| Archive entities | ||||
| Export to Excel | ||||
| Branches | ||||
|
Basic branches Clones and archives. |
||||
|
Advanced branches Changesets and extensions. |
||||
| Export to Excel | ||||
| Designer | ||||
|
Entity & Branch designer Modelling of entities and branches without the technical database jargon. |
||||
|
Easy Lookup Quickly define a lookup to another entity. |
||||
|
Hierarchical Lookup Define a sequence of lookups where the data available in each next lookup is limited (filtered) by the selected value of the previous lookup. For example, Region > Country > City or Brand > Category > Group. |
||||
| Languages | ||||
| Multi-language User Interface | ||||
| Custom language list | ||||
|
Captions in any language Enter the caption or description of the entity columns and branch columns in any language. |
limited | |||
| Security | ||||
|
Role-based access control Define roles and assign roles to users instead of individual permissions. |
||||
|
Object level access A more fine-grained control to provide access control on the level of libraries, entities and branches. |
||||
|
Data-driven security Restrict access to a specific set of data based on your own values. |
||||
|
SSL encryption Every connection is always and automatically encrypted so that your data cannot be read by anyone else. |
||||
|
PBKDF2 256-bit password hashing algorithm Passwords are hashed before they are stored in your database which makes them unreadable and irreversible. |
||||
| SOC-2 compliant data centers | ||||
| Auditing | ||||
|
Basic change audit Registers the user, date and time when creating the row and the user, date and time of the last change to the row. |
||||
|
Audit trail Creates a complete audit log on all changes made to a row. |
||||
|
Audit log retention period The maximum number of days that the audit trail logs are kept. |
365 days | 365 days | 10 years | |
|
Long-term audit log retention period Retention of audit trail logs for up to 10 years to comply with all legal provisions and audit rules. |
optional | |||
| Approval workflow | ||||
|
Single approver Approval of new or modified data and data marked for deletion is performed by a single approval user. A user can never approve their own data entry modifications. |
||||
|
Four-eyes principle Approval of new or modified data and data marked for deletion is performed by two distinct approval users. A user can never approve their own data entry modifications. |
||||
| Data storage | ||||
|
Individual database per client Exceptional functionality at the level of large enterprises for all customers
|
||||
|
Unlimited database size Offering an unlimited database size is rather unique |
||||
|
Unlimited data rows A data row in an entity is the same as a record or row in a database table or even a row in an Excel sheet |
||||
|
Standard backup Multiple backups per day and a retention of the backups for a period of 7 days |
||||
|
Extended backup Multiple backups per day and a retention of the backups for a period of 35 days. |
optional | |||
|
Long-term retention of backups Comply with legislation and audit rules with multiple backups per day and a retention of the backups for a period of 10 years. |
optional | optional | 10 years | |
|
Restore a backup, replacing the existing database Restoring a backup is always on request by submitting a request to our support desk. |
on-demand | on-demand | on-demand | on-demand |
|
Restore a backup in a new temporary database Restoring a backup is always on request by submitting a request to our support desk. The new database will be available for a maximum of 30 days after which the database is deleted. There can never be more than 1 active temporary database. |
on-demand | on-demand | on-demand | |
| Documentation | ||||
|
Inline documentation No more searching for an example or explanation, consult the online documentation directly from the screen via relevant inline links |
||||
| Support | ||||
| SLA is measured and support is provided within the business operating hours of the support desk. | ||||
| 2 business days | ||||
| Next business day | ||||
| 4 hour response time | optional | |||
Pricing and ordering
Go