Self-hosting Lar

Run sync, sign-in, and sharing on a machine you control instead of Lar’s hosted service. The Self-hosted server mode uses the same server package that Lar Cloud runs, at an address you choose. Lar keeps working locally without any server; a server is only needed to move data between devices and people.

Lar is licensed AGPL-3.0. The source release, and with it the public deployment guide, is in preparation, so this page covers connecting the app rather than installing the server.

What a Lar server does

• Sync relay — stores and forwards encrypted updates for workspace sync and shared Objects.
• Accounts — sign-in and device registration, which Cloud and self-hosted sync and sharing need.
• Web publication (optional, off by default) — stores the encrypted snapshots behind published pages.
• AI and capture services (optional, off by default) — an AI proxy and a gateway that receives captured email and messages.

What the server can see

The relay never receives your content keys, so it can’t read your notes or their structure. It can see routing metadata: which accounts share with each other and when, and your public keys. The account service holds sign-in details such as your email address.

Optional services are different. An AI proxy or capture gateway processes the content sent to it, so turn those on only if you trust the machine they run on.

Connect the app to your server

If you already have a server address, for example from whoever runs the server:

1. Open Settings → Sync.
2. Under Sync mode, choose Self-hosted server.
3. Enter the Server URL. It must start with https://; http:// works only for a localhost server when testing.
4. Choose Save.
5. Sign in from Settings → Account.

The Cloud mode uses Lar’s hosted server and has no address to enter. Configure sync explains all four modes.

For current availability, see the FAQ.