Alpacon

For decades, SSH has been the default way to access and manage servers.
It works, it’s powerful, and it’s everywhere.

But as our infrastructure and teams grew, we started noticing more and more friction:

• Managing keys and permissions across many users was messy and time-consuming

• Simple human errors sometimes caused outages or risky changes

• No easy way to collaborate in real-time on the same server session

• Security concerns around credential rotation and temporary access

At some point, we asked ourselves: “Why are we still relying on a tool built in the 90s to handle today’s cloud-native and automated workflows?”

That question led us to start building Alpacon, a platform designed to simplify server access, improve collaboration, and reduce human mistakes.

We’re still early, and we know this is not just our problem. Many developers, DevOps engineers, and security teams must have run into the same issues.

So I’m really curious:

• Is SSH still “good enough” for your workflow?

• Or do you also feel the need for something new?

I’d love to hear your thoughts and experiences.
If you’re interested in sharing more, we also opened a small Discord community to discuss DevOps, security, and infrastructure access:
👉 https://discord.com/invite/wadWh8VsYB

Looking forward to learning from you all!