Connect to infrastructure
Open local, SSH, and Kubernetes terminal sessions from infrastructure cards with tags, links, and credentials nearby.
Lorium brings SSH servers, Kubernetes clusters, encrypted secrets, terminal sessions, and AI runbook generation into one private workspace.
MVP scope: SSH, Kubernetes, encrypted vault, session memory, Markdown runbooks.
Lorium focuses the first release on the path engineers repeat every day: open infrastructure, run commands, capture what happened, and save a useful runbook.
Open local, SSH, and Kubernetes terminal sessions from infrastructure cards with tags, links, and credentials nearby.
Record meaningful commands, output, timestamps, and checks while keeping capture visible, editable, and redacted.
Create editable Markdown runbooks and incident notes from selected session steps, then find them offline later.
Saved to your notes vault
The MVP keeps the operational loop tight: choose a target, work in the terminal, capture the useful trail, and save the generated document beside your notes.
ubuntu@10.10.10.20
Amazon EKS · eu-west-1
ubuntu@10.10.10.40
SSH · prod-api-01 · ubuntu
systemctl status payments-apiSecret-like values redacted before capture
Safely restart the service and verify pod health…
runbooks / production · 2 days agoDiagnosis notes from the May 14 incident…
incidents / payments · 1 month agoCredential rotation procedure and verification…
runbooks / security · 3 months agoLocal, SSH, and Kubernetes sessions with tabs, split view, search, and quick recovery.
ubuntu@prod-api-01:~$ docker compose ps
NAME STATUS PORTS
api Up 3 days 0.0.0.0:8080
worker Up 3 days —
Store credentials locally and link them to the servers or clusters that use them.
••••••••••••••••••••••••Find servers, clusters, secrets, notes, and generated runbooks instantly with Cmd+K.
Pprod-api-01Production
Dprod-db-01Production
Save generated Markdown runbooks into the local notes vault and keep them linked to infrastructure context.
Lorium is local-first by design. Servers, notes, terminal context, provider keys, and secrets live on your device unless you explicitly choose an AI provider for generation.
Begin with a private local workspace, then connect billing and team features only when they become useful. Your operational data does not become a condition of your subscription.
Your terminal memory, runbooks and infrastructure context stay local and available offline.
Connect to infrastructure, capture the session, and save the answer in one private workspace.