I appreciate the reply, but I guess I wasn’t clear on what I was asking.
It’s obvious who this is for in the literal sense, what I mean is: what is the use case for this?
On the homelab front, I don’t see enough need to unify my GUI access, and i have roughly 30 containers to manage. At that point, most homelab admins gravitate to automation.
On the professional front, I can tell you that unifying the keys to mgmt interfaces to critical infrastructure in a single app is not a welcome tool to see on my junior admin desktops. And if it’s simply the interface to mgmt portals without storing keys, then I would have my doubts about a junior admin who hasn’t developed a personal strategy to manage this themselves.
Don’t get me wrong, I’m happy to encourage you to develop this, but the second you write “trying to make a living from this”, you should know that these questions are coming.
If I were across the table from you trying to understand what you’re selling me, I would want to know:
- how do you handle secrets in transit and at rest?
- can I deploy this once and set access for various departments or employees?
- can I find out who has been using the tool?
- how does the app handle updates?
You can see where this is going. If I buy this tool for use by several people, I don’t want to have to wrap it in vault entries and update scripts just to meet compliance with my client’s environment.
Keys spread out? I don’t understand…