This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
TokenTimer
Certificate lifecycle automation without private-key custody
TokenTimer discovers every certificate, token, secret and license you own, alerts the right people before expiry, and automates renewal where it matters. Cloud-managed SaaS or self-hosted, metadata-only security, source-available on GitHub.
We originally launched TokenTimer around a simple problem: infrastructure assets expire, ownership gets lost, and teams often discover it when something breaks.
Since then, we kept seeing the same limitation: knowing that a TLS certificate expires in 15 days is useful, but somebody still has to renew it, deploy it, reload the service and verify that the right certificate is actually live.
That led us to build CertOps into TokenTimer.
TokenTimer now combines managed certificate inventory with customer-side certificate operations. The key architectural decision was that private keys should never need to enter our control plane: key-bearing work stays in infrastructure controlled by the customer.
We also still handle the broader expiration problem: API keys, secrets, licenses and other time-bound assets.
I’d especially appreciate feedback from DevOps, SRE, platform, security and PKI teams:
Where does certificate lifecycle automation still hurt in your environment: discovery, ownership, renewal, deployment, or verification?
No comment highlights available yet. Please check back later!
About TokenTimer on Product Hunt
“Certificate lifecycle automation without private-key custody”
TokenTimer was submitted on Product Hunt and earned 8 upvotes and 1 comments, placing #61 on the daily leaderboard. TokenTimer discovers every certificate, token, secret and license you own, alerts the right people before expiry, and automates renewal where it matters. Cloud-managed SaaS or self-hosted, metadata-only security, source-available on GitHub.
TokenTimer was featured in Productivity (659.9k followers), Developer Tools (518.8k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 268.7k products, making this a competitive space to launch in.
Who hunted TokenTimer?
TokenTimer was hunted by Franz. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how TokenTimer stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Franz
Hey Product Hunt 👋
If you don’t already know TokenTimer, here is a quick explainer video:
https://www.youtube.com/watch?v=LJxvw6wXR3o
We originally launched TokenTimer around a simple problem: infrastructure assets expire, ownership gets lost, and teams often discover it when something breaks.
Since then, we kept seeing the same limitation: knowing that a TLS certificate expires in 15 days is useful, but somebody still has to renew it, deploy it, reload the service and verify that the right certificate is actually live.
That led us to build CertOps into TokenTimer.
TokenTimer now combines managed certificate inventory with customer-side certificate operations. The key architectural decision was that private keys should never need to enter our control plane: key-bearing work stays in infrastructure controlled by the customer.
We also still handle the broader expiration problem: API keys, secrets, licenses and other time-bound assets.
I’d especially appreciate feedback from DevOps, SRE, platform, security and PKI teams:
Where does certificate lifecycle automation still hurt in your environment: discovery, ownership, renewal, deployment, or verification?