Luwu, on your servers.
The same app, command and encryption as Luwu, with the accounts, the audit log and the admin controls on machines you run. Your people sign in with your identity provider and reach their machines from wherever they are; what they type never leaves their devices unencrypted, and your security team can see who opened what and stop it.
Your people, your identity provider
Sign in with a one-time email code, a password, or OpenID Connect (Okta, Entra ID, Google Workspace). Accounts live in your server's database. Nothing about your people is stored at Luwu.
A record of every session
Sign-ins, terminal sessions and who typed in them, uploads and downloads with their paths, shared windows, and agent runs, reported by each computer to your server. Keep it as long as your policy says, and export it as JSONL or CSV.
Stop anything, from one place
Block an address, an account or a device, or end a terminal session or an agent run. Computers apply the decision within a minute, relays within 30 seconds.
Same keys, same guarantees
Every device has its own key and every connection is encrypted end to end. Your server vouches for which devices belong to whom and never sees what is typed or read. Computers never share ~/.ssh, cloud credentials or .env files.
One build server, each person as themselves
On a shared Linux machine, Luwu maps each member to their own Unix user. People see only their own sessions and files, and taking someone off the map ends their access within two minutes.
Relays: Luwu's, or your own
A phone and a computer connect directly when the networks allow it, and through a relay otherwise. A relay passes along encrypted bytes it can't read. Enterprise gives you two ways to run them:
Public relays, under your license
Your server tells Luwu which devices are allowed, and they use Luwu's relays in Los Angeles, Hong Kong and Frankfurt. Nothing to run; the license covers it.
Exclusive relays
Run the relay yourself, on your network or at your cloud provider, or have Luwu dedicate one to you. Only your devices use it, and the traffic never touches shared machines.
How it starts
- 1
One binary, your database
luwu-serverruns on Linux with SQLite out of the box, or with PostgreSQL. It serves the API, the sign-in pages and the admin console. - 2
A license per seat, per year
The license is a signed file, checked offline. It names your seats, your relays and your server's key, with a 14-day grace period after it expires.
- 3
The same app and command
People open the Luwu app or run
luwu login, enter your server's address, and sign in. Everything else works as it does on luwu.dev.
Talk to us
Tell us how many people and computers you have and whether you want public or exclusive relays, and we send a quote.