GrantSSH.com

We didn’t want to replace SSH. We wanted to keep the normal SSH workflow, but make access easier to grant, revoke, schedule, and audit. That’s why we built GrantSSH. https://grantssh.com/blog/building-grantssh

A useful SSH access audit should answer: Who can access each server? As which account? When should that access end? What activity happened while it was active? https://grantssh.com/blog/audit-ssh-access

Scheduled SSH access is useful for more than contractors. On-call windows, maintenance work, temporary support, client projects, short-term cover. Access should match the actual need. https://grantssh.com/features

GrantSSH is simple usage-based pricing. First server and first 2 team members are free. After that it’s per server and per team member, with no plans or contracts. https://grantssh.com/pricing

Web agencies and dev shops often end up with SSH access spread across clients, contractors, projects, and environments. GrantSSH helps keep that access scoped, temporary, and visible. https://grantssh.com/use-cases/agency-client-server-access

GrantSSH only works with public SSH keys. No private keys. No SSH passwords. No shell access to your servers. The open-source agent runs on your infrastructure. https://grantssh.com/security

During an incident, the priority is getting the right person onto the right server quickly. The cleanup afterwards is the bit people forget. GrantSSH gives you access windows that close themselves. https://grantssh.com/use-cases/on-call-ssh-access

We made some free SSH tools that run in your browser. Inspect public keys, check authorized_keys, generate ssh-keygen commands, and build SSH config blocks. Nothing gets uploaded. https://grantssh.com/tools

The scariest SSH keys are often the ones nobody remembers adding. Old laptops, old contractors, one-off fixes, forgotten project access. That drift is exactly what GrantSSH was built to reduce. https://grantssh.com

GrantSSH isn’t a bastion host or SSH proxy. Users still connect with their normal SSH client and key. We just help control when that public key should exist on the server. https://grantssh.com/how-it-works

Offboarding SSH access shouldn’t mean hunting through every server and every authorized_keys file. Revoke access centrally, then let the agent clean up the keys locally. https://grantssh.com/use-cases/developer-offboarding

Contractor SSH access is easy to grant and easy to forget. GrantSSH lets contractors use normal SSH, while you control which server/account they can access and when. https://grantssh.com/use-cases/contractor-ssh-access

Temporary SSH access should actually be temporary. Give someone access for the project, incident, or maintenance window, then let it expire without relying on calendar reminders. https://grantssh.com/features

SSH access quietly becomes a mess. Old keys. Forgotten contractors. Manual cleanup. Nobody fully sure who can still log in. GrantSSH helps keep access time-bound, visible, and easier to clean up. https://grantssh.com

We didn’t build GrantSSH because SSH is broken. SSH is great. The messy bit is access: adding/removing people, temporary access, old keys, and knowing who logged in. That’s what we wanted to solve without turning it into an enterprise project. https://grantssh.com/blog/building-grantssh

GrantSSH.com is live 😎 A new way of managing your teams SSH access to servers without the mess of having to manually add and remove them from your authorized_keys files! #buildinpubic #servermanagement