Want to run it yourself?
That’s the point.

Self-hosting is first class here.

Most services treat self-hosting as a dare: a compose file, a reverse proxy, a certificate dance, and a wall of "community supported". Eleven treats it as a right. The server is one static binary with everything inside — the app, the database engine, the TLS front door — and it installs itself.

Try it before you install anything

curl -fsSLo lchat "https://github.com/elevenmessenger/releases/releases/download/server/lchat-$(uname -s | tr '[:upper:]' '[:lower:]')-$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/')"
chmod +x lchat
./lchat try

That’s a complete, end-to-end-encrypted space served from whatever machine you ran it on — a Mac, a Linux laptop, a Raspberry Pi — with a real public address like try-x7k2m.11ch.at. No ports to open, no domain, no certificate, no root. Invite someone; chat from any browser or the apps. Stop the command and the trial address politely retires — your space’s data stays on your machine, in lchat-try.db, ready for a permanent home.

How can that work? Your machine dials out to our tunnel gateway, which lends the trial a name under our wildcard certificate — details on the architecture page. Trials live for a day at most; keepers get the real install below.

The whole install

curl -fsSL https://github.com/elevenmessenger/releases/releases/download/server/install.sh | sudo bash

That downloads the latest stable release for your architecture, verifies its published checksum, and sets the box up: a locked-down service user, the TLS router on ports 80/443, and hourly auto-updates with a health check and automatic rollback. (Prefer not to pipe to shell? Download the script from the same URL and read it first — it’s short.)

Your first space

Point a DNS record at the box (chat.example.com → your box), then:

lchat add-instance chat.example.com

It prints a one-click setup link. Open it, pick a name, and Eleven walks you through setting up the space and inviting people. The certificate issues itself on the first request — no certbot, no nginx, no reverse proxy. Run add-instance again for the club: every space is fully isolated, sharing nothing.

What you need

A small Linux box — Ubuntu or Debian, x86_64 or ARM. 1 GB of RAM is plenty; a €4-a-month VPS works.
A domain or subdomain you can point at it.
Ten minutes, generously.

Nothing second-class about it

The apps just work. Your members use the same web, Mac, and iPhone apps against your box as against ours.
Push notifications work through the shared relay with zero configuration — your box never holds any Apple credentials, and the relay only ever sees ciphertext.
Updates keep coming. Your box follows our signed release feed on the channel you choose (stable, beta, edge — or off), health-checked with automatic rollback.
Bots too, optionally. The same binary runs the AI helpers, with the keys held on whatever machine you choose.
The point: even on your own box, the server sees only ciphertext. Self-hosting isn’t how you get privacy (that’s built in). It’s how you get sovereignty.