SLA/Support Tiers and Plan Limits

An Akeyless Client is a unique identity, such as an application, user, or machine, which consumes secrets and/or authenticates itself through the Akeyless Secret Orchestration. Registration and reception of the same uniquely identified client are counted as one client per month.

A secret is any form of password, credentials, api-key, or token, certificate, encryption key or signing keys, either statically set or dynamically created.

Dynamic secrets are secrets that are generated every time access is required, and automatically expire after a given time frame.

Rotated secrets enable you to protect the credentials for privileged-user accounts such as an Administrator account on a Windows server, a root account on a Linux server, or an Admin account on a network device, by resetting its password.

Akeyless RBAC follows the least privilege principle to limit access rights for machines/human users to the bare minimum of permissions they need to perform their work.

The Akeyless Universal Identity authentication method enables you to identify and provide secrets for your legacy machine identities. This authentication method also solves the secret zero problems by providing an inherited identity derived from the parent system together with an ephemeral token for continuous authentication.

Leveraging Akeyless’ unique Distributed Fragments Cryptography (DFC™), your encryption keys never exist as a whole. They are instead created as fragments on different regions and cloud providers and never combined, not even during the encryption/signing process itself. To ensure that you are the exclusive owner of your keys, one of the fragments is created in your environment and cannot be accessed by Akeyless.

The Gateway Cache improves performance when fetching secrets. The Proactive Cache enables storing secrets in the Gateway Cache in advance.

Refers to Akeyless SaaS service only, based on our multi-region and multi-cloud operations.

The number of regions in which Akeyless would respond to the customer’s workload requests. Having more than one is usually recommended for customers who obtain multi-region workload operations, in order to improve latency or meet multi-region data localization requirements.

The maximum number of technical contacts from the customer that can interface with the Akeyless Customer Success Team

Overuse of the daily quota is automatically allowed, yet an overuse will be counted as an additional client. For example, when the cap is 10K, every 10K transactions above the first capped 10K will be considered as an additional client