Locoris
English

Select language

Download

Self-hosted sync

Operate the remote layer yourself.

A deliberate advanced path for people and organizations prepared to manage deployment, storage, updates, TLS, monitoring and backups.

Open server sourceSync documentation

Control with responsibility

Self-hosting moves trust. It does not remove operations.

You choose the infrastructure and retention policy, but you also own uptime, server hardening, capacity, backups and recovery testing.

Locoris self-hosted synchronization setup
Endpoint, persistence and vault binding remain explicit responsibilities of the operator.

Two supported paths

Choose the server, not a pile of setup choices.

Docker is the always-on production path. Locoris Server is the visual desktop path. Version 0.1.7 uses the same SQLite + vault-file runtime and pairing flow in both.

Docker / NAS

One multi-architecture image for Linux amd64 and arm64, with numbered tags, health checks, SBOM, provenance, and a signed manifest.

linux/amd64linux/arm64
Locoris Server

A visual local server with pairing, network diagnostics and update status. New macOS builds support Apple Silicon only.

macOS arm64Windows x64Linux x64

Pin a numbered version, verify `SHA256SUMS.txt` or the Cosign manifest signature, and back up the complete data volume before updating.

Release 0.1.7

Version 0.1.7

Install the current server with a pinned version.

Both paths use the same pairing flow and portable data layout. Docker is best for an always-on machine; Locoris Server adds a visual dashboard for a personal computer.

Recommended for servers

Docker / NAS

  1. 01Download the verified Compose files
    mkdir locoris-server && cd locoris-server
curl -fsSLO https://raw.githubusercontent.com/locoris/locoris/server-v0.1.7/infra/docker/personal-server/compose.example.yml
curl -fsSL https://raw.githubusercontent.com/locoris/locoris/server-v0.1.7/infra/docker/personal-server/.env.example -o .env
sed -i 's/^LOCORIS_SERVER_VERSION=.*/LOCORIS_SERVER_VERSION=0.1.7/' .env
  2. 02Set the reachable address in `.env`

    Use a LAN address for a trusted local network, or an HTTPS address through a reverse proxy or private network for remote access.

  3. 03Start and open the pairing invitation
    docker compose -f compose.example.yml pull
docker compose -f compose.example.yml up -d
docker compose -f compose.example.yml logs -f
linux/amd64 · linux/arm64SQLite + filesSingle data volume

Your endpoint

Deploy the standalone server behind HTTPS and connect it as an external synchronization method.

Your hardening

Control access, secrets, TLS, firewall policy, updates and abuse prevention for the deployment.

Your recovery

Back up both server data and local vaults, then test that restoration works before relying on it.

Before deployment

The minimum operational checklist.

Choose persistent storage

Never point production data at temporary directories. Define ownership and a tested backup destination.

Protect the endpoint

Use HTTPS, strong secrets, restricted administration, logging and a clear update process.

Connect deliberately

Add the endpoint in External sync, verify access and bind only the intended local vaults.