Secretify keeps evolving based on real feedback from security teams and IT professionals. This release brings several meaningful improvements: a new way to retrieve secret links after you’ve created them, modern authentication options, machine identity support, end-to-end encrypted file transfers, and a refreshed interface with more accessible secret types. Here’s what changed and why it matters.
Unlock Methods: Retrieve Your Secret Link After Creation
Previously, once you created a secret in Secretify you had exactly one opportunity to copy the link. Close the tab too fast, lose focus for a moment, and the link was gone. You’d have to start over.
With the new unlock method, that constraint is lifted. After creating a secret you can unlock and retrieve the link at any later point, as long as you know the password or PIN you set.
How It Works
When you create a secret, Secretify generates a key that gets embedded in the link. This key never reaches Secretify’s servers. It only exists in the URL.
When you enable an unlock method, that same key is also encrypted using a key pair tied to your password or PIN. The encrypted copy is stored server-side, but only your password or PIN can decrypt it.
To retrieve the link later, just enter your password or PIN. This unlocks the key and gives you back the original link.
This approach keeps Secretify’s security guarantees intact while giving you a practical recovery path. No more recreating secrets because the browser tab closed too early.
OIDC and Google Authentication
Managing separate credentials for every tool adds friction and creates password hygiene risks. Secretify now supports OpenID Connect (OIDC) and Sign in with Google, so you can log in through your existing identity provider.
For teams using Okta, Azure AD, or a self-hosted IdP, this means Secretify slots directly into your current access management setup. User provisioning, session policies, and offboarding all follow your existing rules. No separate Secretify credentials to manage.
Google authentication covers the common case where teams run on Google Workspace and want a simple login experience without setting up a full IdP.
Ready to try the new features?
Token-Based Machine Identity (Early Access)
Automated pipelines need to share secrets too: CI/CD systems provisioning credentials, scripts rotating API keys, deployment tools distributing certificates. Until now, these workflows had to work around Secretify or use a human account.
Token-based machine identity gives non-human actors a proper, auditable identity within Secretify. You create a token scoped to the operations your automation needs, and that token authenticates the machine without any human in the loop.
This is particularly useful for infrastructure teams who want to bring secret sharing under the same governance model as the rest of their toolchain.
End-to-End Encrypted File Sharing (Early Access)
Text secrets are one thing. But teams regularly need to share files too: configuration bundles, key material, certificates, signed documents. Until now, Secretify covered text. Now it covers files too.
End-to-end encrypted file upload and download brings the same security Secretify applies to text secrets to binary files. Files are encrypted on your device before they leave it, and decrypted only by the intended recipient. Secretify cannot access the file contents at any point.
Do you have questions about any of these features or want to get file encryption enabled for your tenant?
Secret Visibility: Control Who Can See What
Every secret you create can now be assigned a visibility level:
- Private: only you can see and access it. Useful for personal credentials or secrets you’re preparing before sharing.
- Internal: visible to any authenticated user within your tenant. The right default for team-shared secrets that shouldn’t be public.
- Public: accessible to anyone with the link, no authentication required. Suited for one-off sharing with external parties or clients.
Instead of managing access through workarounds, visibility is now an available preference when creating a secret.
Improved UI and More Accessible Secret Types
The interface has been updated with a cleaner layout and a reworked set of custom secret types. Instead of a blank text field for everything, you now get purpose-built input forms for common secret patterns: credentials, API keys, certificates, and more. Each type shows the right fields with clear labels, making it harder to accidentally put information in the wrong place.
The goal is to reduce friction, especially for team members who use Secretify occasionally. You shouldn’t have to remember the right format for an API key. The interface guides you.
Available on Self-Hosted Deployments Too
Every feature in this release (unlock methods, OIDC, machine identity tokens, file encryption, secret visibility, and the updated UI) is also available in the self-hosted version of Secretify. If you run your own instance, update to the latest release to get them all.
Self-hosting gives you full control over your infrastructure, data residency, and network isolation. Combined with OIDC integration and machine identity tokens, it’s a strong fit for organizations with strict compliance or sovereignty requirements.
No Tenant Setup Required Anymore
Previously, signing up for Secretify meant going through tenant creation before you could do anything useful. That was a barrier for anyone who just wanted to try it out.
That’s gone now. You can sign up and start using Secretify directly for free. No tenant setup or configuration required. You land straight in the app and can create and share secrets right away.
If you later want your own isolated environment (custom domain, your own user directory, branded interface) you can upgrade to a dedicated tenant at any point. But that’s your choice to make once you’ve seen how it works, not a prerequisite to getting started.
Key Takeaway
Security That Fits How You Actually Work
Every feature in this release came from real friction we saw teams run into. Losing a link because a tab closed, onboarding automation without a clean identity model, wanting to log in the same way you log in everywhere else or needing to share a file, not just text.
None of these are edge cases. They’re the everyday reality of how security and IT teams work. Secretify is built to meet that reality.