SSHID is a self-hosted hub for SSH public keys. Save your keys once, share a memorable URL, and authorize them on any server with one command — no manual copying, no duplicate authorized_keys entries, and no need to pass private keys around.

Instead of copying public keys manually between machines, a user can save their public SSH keys once in SSHID and then install them on a server with a short command:

curl -sS https://ssh.hsp.ovh/username | bash

For example:

curl -sS https://ssh.hsp.ovh/ghostcompiler | bash

The public browser page at the same URL shows a polished command page with copy buttons. Command-line clients receive an installer script.

SSHID makes SSH key distribution easier for developers, server admins, and teams who frequently need to authorize the same public keys on new servers.

Use it to:

• Store SSH public keys under a user account.
• Share a memorable public install URL.
• Install saved SSH keys on a server with one command.
• Avoid duplicate entries in ~/.ssh/authorized_keys.
• Keep the private SSH key on the user's machine.

SSHID only stores public keys. It should never receive or store private keys.

• User registration and login.
• Custom public username for each account.
• Dashboard for adding, listing, and deleting SSH public keys.
• SSH public key validation before saving.
• Duplicate key detection using a stable key hash.
• Public command page at /{username} for browsers.
• Bash installer script at /{username} for command-line clients such as curl.
• Raw key endpoint at /{username}.keys.
• Legacy installer endpoint at /{username}/install.
• Installer creates ~/.ssh, fixes permissions, validates fetched keys, and skips keys already present in authorized_keys.

For a browser request:

https://ssh.hsp.ovh/ghostcompiler

SSHID shows a public page with commands and copy buttons.

For a command-line request:

curl -sS https://ssh.hsp.ovh/ghostcompiler | bash

SSHID returns a bash installer script. The script fetches:

https://ssh.hsp.ovh/ghostcompiler.keys

Then it appends missing valid public keys to:

~/.ssh/authorized_keys

• Laravel 13
• PHP 8.3+
• Inertia.js
• React 19
• Vite
• Tailwind CSS
• shadcn-style UI components
• SQLite or any Laravel-supported database

• PHP 8.3 or newer
• Composer
• Node.js and npm
• SQLite, MySQL, PostgreSQL, or another Laravel-supported database

Clone the repository:

git clone <repository-url>
cd ssh

Install PHP dependencies:

composer install

Install JavaScript dependencies:

npm install

Create the environment file:

cp .env.example .env

Generate the application key:

php artisan key:generate

Create the database if you are using SQLite:

touch database/database.sqlite

Update .env for SQLite:

DB_CONNECTION=sqlite
DB_DATABASE=/absolute/path/to/database/database.sqlite

Run migrations:

php artisan migrate

Start the development servers:

composer run dev

Open the app:

http://127.0.0.1:8000

If port 8000 is already in use, Laravel may start on another port such as 8001.

Run the PHP test suite:

php artisan test

Run Laravel Pint:

./vendor/bin/pint

Build frontend assets:

npm run build

Run only Vite:

npm run dev

Public command page and CLI installer:

GET /{username}

Raw public keys:

GET /{username}.keys

Installer script:

GET /{username}/install

Dashboard:

GET /dashboard

Update username:

PATCH /dashboard/username

Add SSH key:

POST /dashboard/keys

Delete SSH key:

DELETE /dashboard/keys/{key}

• Only public SSH keys should be submitted.
• Private keys must stay on the user's machine.
• The installer uses ssh-keygen to validate keys before appending them.
• Duplicate saved keys are detected by hashing the key type and public key body.
• The install command pipes a script into bash; users should only run commands from a SSHID instance they trust.

Memorable SSH public key hosting and one-command server authorization for developers and teams.

This project is open-sourced under the MIT license.