Lisa Blog

Introducing Bridge: Lisa Server's face in a browser

· The Lisa team
serverbridgehosting

Lisa comes in flavours built from the same frameworks, the same contracts and the same release. Lisa Server is the one with no display and nothing graphical in it: the substrate, the core daemons, and one listening service. That service is Bridge.

Bridge is to the server what the Shell is to the desktop: the whole machine’s management surface, in a browser. You open it from a phone or another computer, sign in with the machine’s own account, and steer the machine from there. Nothing on a desktop needs it.

Two halves, one sign-in

Bridge has two areas, and they are deliberately kept apart.

System is the machine itself: services, network and firewall, storage, users, scheduled tasks, logs, a terminal, and Software Update. The reference for this half is Ajenti, the long-standing Linux server panel.

Hosting is what the machine runs for you: websites and services as containers, deployed from an image, a repository or local source, with a catalogue of one-click templates, the images it holds, its storage and its proxy. The reference for this half is Basepod, a hosting tool of ours with CapRover’s shape: Go, rootless Podman, Caddy with automatic certificates, and a push command. Basepod became Bridge’s Hosting half.

The Dashboard reads from both: the release and its update state, uptime and load, CPU, memory and disks, the network, whether the firewall is on, how many applications are running, stopped or failed, and the latest activity. Every tile links to the area that owns it, and nothing is changed from the Dashboard itself.

What neither reference has is the thing that holds them together: one sign-in, one set of permissions and one activity record for both halves.

Your machine’s account, nobody else’s

Bridge creates no accounts of its own. You sign in with the machine’s own account. Bridge hands the name and password to the machine’s own daemon, and the machine answers from its own password store. An administrator on the machine is an administrator in Bridge; anyone else reads.

The first password is the one the installer showed you once. It is marked must change: the first sign-in asks for a new one before letting you in. There is no first-visitor setup page. Basepod had one, and on a server it would let whoever reached the page first claim the machine. On Lisa Server that route answers gone, and recovery is the console.

Built to be the only door

Bridge is the only process on a Lisa server that listens on the network. Every other daemon is denied the network in its own unit.

Its proxy answers on ports 80 and 443. Port 80 redirects to HTTPS and serves nothing else. Bridge’s own API stays on the loopback, behind the proxy, and every answer carries strict security headers. Give the machine a domain with a wildcard record, and Bridge answers at lisa.<your domain>. Each hosted application gets its own <app>.<your domain>, with a Let’s Encrypt certificate issued at the name’s first visit. Certificates are issued only for names Bridge knows, so a stranger cannot spend the domain’s certificate allowance by knocking on random names.

Bridge also doesn’t update itself. It arrives inside the server image, and the image is what updates, whole and signed, like every Lisa release.

From a rented box, one command

On any box with root over SSH, whether a Hetzner server, a VPS anywhere or a machine at home, running whatever Linux the provider put on it:

curl -fsSL https://os.lisaos.dev/install | sh

It asks three things: the domain Bridge will answer at, the machine’s name, and the password. If you have no domain, the machine gets a name of Lisa’s own, <machine>.lisaos.cloud. The script turns the box into Lisa Server, and lisa setup brings Bridge up, with the firewall on and SSH, HTTP and HTTPS already allowed. Nothing on that list is left for an administrator to do by hand.

From a desktop, the same actions are the lisa server commands: login, push, apps, logs. They speak to Bridge’s API; there is no second tool.

What is not done

We prefer to say this plainly.

  • No server runs Bridge today. The last one took five releases through the channel, proved them, and was deleted the same evening. Our rule is that a test box is installed, proven and deleted, so nothing idle is paid for. The next machine installs with the one command above.
  • Some views are designed but not yet served: the Assistant in a browser, People, Sharing and the Ledger.
  • Some Hosting actions still go to Podman directly: deploying, pushing, building and naming an app don’t yet go through the server’s own container daemon.
  • Bridge’s stack is the one it inherited: Go, a Nuxt web page, and Caddy. A rewrite is for later, and only if this one doesn’t hold.

All of it is written down, line by line, on Bridge’s page in the docs.

← All posts