Shellius documentation

Shellius replaces static SSH keys and shared RDP passwords with short-lived certificates, reviewed access to production, and one audit trail. Your servers trust a single certificate authority; people get access that expires on its own.

Start the quickstartHow Shellius works

• Connection Shellius opens for you
• Connection your own machine opens
• API call

Shellius sits between your people and your fleet. It signs certificates, opens browser sessions itself, and answers every host that asks whether a certificate is still good.

Guides

QuickstartFrom an empty Docker host to a first certificate login.Install with DockerSecrets, Compose files and first boot.Bootstrap a hostPut a server behind the certificate authority.Write access policiesWho may reach what, as whom, and for how long.Approvals for productionMake every production session pass a second person.Invite your teamUsers, roles and the permission model.Record sessionsReplay what happened in an SSH session.Use the terminal clientRequest and connect without leaving your shell.

About Shellius

How Shellius worksThe parts, and a request from start to refusal.Shellius vs. static keysWhat changes, and what honestly does not.Network reachabilityWhen people need a VPN, and when they do not.Self-hosted vs. cloudWho runs it, and who holds the CA.

Running it

HardeningBefore real hosts go behind it.BackupsThe database, recordings and one key.TroubleshootingFrom a symptom to a cause.