Akeyless sells a secrets, keys and certificates platform with a SaaS control plane and gateways in the customer's network. Pages here cover replacing it with self-hosted OpenBao or Infisical.
Comparing Akeyless's SaaS control plane and gateways with OpenBao run entirely in your own infrastructure: key custody models, static, rotated and dynamic secrets, PKI, availability when the internet link fails, and licensing versus operating effort.
Comparing Akeyless with self-hosted Infisical: secrets, rotation and dynamic secrets, PKI and KMS, gateways versus a fully self-hosted deployment, Kubernetes integration, and what each charges for beyond the free tier.
Moving from Akeyless to OpenBao: reading static secret values item by item, re-creating rotated and dynamic secret targets as OpenBao engines, issuing a new PKI hierarchy, switching clients from Akeyless auth to OpenBao auth methods, and retiring gateways.
Cost components: Akeyless Free plan limits and quote-based Enterprise pricing, gateway hosting, against OpenBao with no license fee, servers, storage, optional HSM and the people who run it, plus migration effort.
Akeyless's migration tooling is built for moving secrets into its platform. This page covers retrieving static secrets and versions through the CLI or API before leaving, re-creating rotated and dynamic secret targets and certificates elsewhere, and planning the cutover.
Akeyless keeps its control plane in the cloud with gateways on site. For networks that cannot depend on an external control plane at all, this page covers running OpenBao or Infisical fully inside the boundary, including unseal, updates and HA design.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.