Ecosystem

One account. One Graph. Every screen.

Desktop, the lisaos.dev portal, mobile, and TV are not four apps — they are four shells over the same LisaOS. One identity signs you in, one Graph holds your data, and one operator mesh runs your work, so what you start on one surface is already there on the next.

Four surfaces, one spine. Sync is the architecture, not a feature.

Surfaces

Pick a screen.

Each surface is the right shape for where you are — a full workstation on the desktop, your portal in any browser, a thumb-sized companion on your phone, an ambient glance on the TV.

Desktop

Available
macOS · Windows · Linux

The full OS. Every Space, the Operator, files, memory, themes, and automations — and the preferred executor for your automations whenever it is running.

Download →

Web portal

Available
lisaos.dev

Everything around the OS, in the browser — your account, organisations, the developer portal, domains, and delivery. Nothing to install.

Open portal →

Mobile

Coming soon
iOS · Android

A device-bus companion. Ask from your phone and it runs live on your online desktop operator. A cloud fallback for when the desktop is offline is on the way.

TV

Preview
Android TV

An ambient, voice-driven dashboard. Speak a query and the inference API composes a screen-spec on the fly — clock, weather, or anything you ask for.

The spine

Why they stay in sync.

There is no per-device database to reconcile and no sync conflict to resolve, because there is only one of each thing underneath.

One identity

A single account and session sign you in everywhere. The same token authorises desktop, web, mobile, and TV — no per-device accounts, no separate logins.

accounts

One Graph

Every Space reads and writes the same Graph. Your user and org are resolved from the token server-side, so the data you see is identical on every screen.

graph.lisaos.app

One operator mesh

Your work runs on a machine you own. Asks from any surface already route to your online desktop operator; the execution mesh — Conductor scheduling to your desktop first, the cloud as fallback — is rolling out to keep automations running when the desktop is closed.

conductor + space-runtime

Shared services

The same APIs back every client — inference for the Operator, source and developer for code and publishing, marketplace for the Space Store.

inference · source · developer