Secrets Manager for secure application credentials.
Keep every access under control.
Secure API keys, database credentials, tokens and certificates in one centrally managed platform. Uniqkey Secrets Manager helps you manage machine access and maintain visibility into secret activity.
.png)
Application secrets are everywhere.
They shouldn’t be.
Application credentials often end up scattered across source code, configuration files and local environments. As systems grow, it becomes harder to control who or what can access them. Uniqkey Secrets Manager brings credentials into one centrally managed platform, with restricted access, client side encryption and visibility into secret activity.
Remove secrets from unsafe places
Move application credentials out of source code, local files and scattered environments.
Give machines only the access they need
Restrict applications and services to the specific secrets and actions they require.
Stay in control when things change
Review secret reads and changes, restore previous versions and recover recently deleted secrets.
Assign individual API keys to applications, servers and automated processes. Restrict access to specific secret paths with read or write permissions, so services only access the credentials they need. API keys can be activated, deactivated or deleted centrally.
Applications can retrieve credentials through the Uniqkey API or Command Line Interface (CLI), available for Windows, macOS and Linux. Uniqkey verifies the API key and its permissions before returning encrypted data for local decryption. .NET and Kubernetes integrations are also supported.
Maintain visibility into secret activity with audit logs that record reads and changes, including which API key was used. Review previous versions, roll back incorrect changes and recover deleted secrets within 30 days. Clear audit trails also make it easier to support internal reviews, governance and compliance requirements.
Works with
any programming language.
C# / .NET, JavaScript / TypeScript, Node.js, Python, Java / Kotlin, Go, PHP, Ruby, Rust, and PowerShell / Bash for automation and deployment scripts.
Your secrets stay encrypted. Even from us.
Uniqkey Secrets Manager protects secret values, descriptions and tags with AES-256-GCM client side encryption. Secrets are decrypted locally, while Uniqkey’s servers store encrypted data without access to plaintext secret values.
Client side encryption
Secret values are encrypted and decrypted locally using AES-256-GCM before sensitive data reaches Uniqkey.
Plaintext stays local
Decrypted secret values remain on the client side and are never exposed to Uniqkey infrastructure.
Encryption by default
Secret values, descriptions and tags are protected as part of the standard Secrets Manager architecture.
Trusted by leading European organisations.
Loved by customers, hated by hackers.
.svg)
.avif){kind=small}
_HighPerformer_HighPerformer.svg)
Still have questions?
No problem.
A secrets manager securely stores and controls access to credentials used by applications, servers and automated processes. These include API keys, database passwords, tokens and certificates. Instead of keeping credentials in source code or local configuration files, applications can retrieve them securely when needed.
A password manager helps people securely access websites and applications. A secrets manager is designed primarily for machine-to-machine access, allowing applications, servers and automated processes to retrieve the credentials they need. Uniqkey provides both capabilities within the same platform.
Secret values, descriptions and tags are encrypted on the client side using AES-256-GCM encryption. Uniqkey's servers store encrypted data and do not have access to plaintext secret values. Paths and certain metadata remain readable to support organisation and auditing.
Yes. API keys can be restricted to specific paths and read or write permissions. For example, a development application can be given access to development credentials without being able to retrieve production secrets.
Yes. Audit logs record secret reads and changes, including which API key was used. Using a separate API key for each application or service makes it easier to identify which system accessed a secret.
Yes. Secrets Manager supports version history and rollback, allowing administrators to review and restore previous secret values. Deleted secrets can also be recovered within 30 days.
No. Updating a secret in Uniqkey does not automatically change the corresponding credential in an external application, database or service. The external credential must also be updated, and applications must be configured to use the new value.
Uniqkey Secrets Manager supports compliance efforts by helping organisations maintain stronger control over application credentials and machine access. Scoped permissions, client side encryption, audit logs and version history provide clearer documentation of how secrets are stored, accessed and changed. This can support internal reviews, security governance and audit readiness. Secrets Manager does not make an organisation compliant on its own, but it can help provide the access controls and evidence needed to support broader compliance requirements.
Secrets Manager is available as an add-on to the Uniqkey platform. You can find it in your Uniqkey Admin Portal. Contact your Customer Success Manager or Uniqkey partner to learn more about enabling it for your organisation.
