Your server, your chat.

Yakyard runs on your own Linux server now. Docker runs it, Caddy handles HTTPS, and every message, file and setting sits in one volume on your disk.

A channel on a server with no Cloudflare token: the voice note plays, and under it Yakyard says transcripts are off on this server

Up in about 15 minutes.

You need a Linux server with Docker Compose v2, a domain pointing at it, and ports 80 and 443 open. 1 GB of memory is enough for a small team.

git clone https://github.com/yakyard/yakyard.git
cd yakyard
cp .env.example .env
# set DOMAIN and SETUP_TOKEN
docker compose up -d

When docker compose ps says healthy, open https://your-domain/setup and create the owner account. Caddy gets the certificate by itself.

Same app, your hardware.

The Worker runs in workerd, the open-source runtime Cloudflare Workers is built on, through Wrangler's local mode. The database, files and background jobs live in one Docker volume, and the database is brought up to date every time Yakyard starts.

Everything you use today

Channels, threads, DMs, calls, search, phone notifications, Google sign-in, the Slack import and locked conversations. Same code as on Cloudflare. Photo previews are made on your server.

Yakyard in a browser: a channel with messages, a thread, reactions and a voice note

Voice notes keep working

They record, send and play. Transcripts come from Workers AI, so they need a free Cloudflare token. Without one, each note says so.

A voice note on a phone, with the line Transcripts are off on this server

Backups and updates.

One command backs up everything: messages, files, voice notes and settings. Copy the file off the server.

  • Run sh docker/backup.sh. It stops Yakyard for a few seconds so the database is copied whole, and saves a dated file in the backups folder. To put one back, run sh docker/restore.sh. It asks first.
  • Release tags publish the image to ghcr.io/yakyard/yakyard. latest follows releases, or pin one in .env, like YAKYARD_VERSION=2.2.0, and update when you choose.
  • On every change, CI builds the image and runs the full security suite against the container, then restarts it and checks nothing was lost.

Cloudflare or your own server.

Don't want to look after a server? Stay on Cloudflare. Want your chat on hardware you control, with no daily limits? Use Docker.

Running Yakyard on Cloudflare compared with your own server
WhereSetupCostLimitsTranscriptsUpkeep
CloudflareDeploy button or four commands, about 30 minutes$0 for most teams up to about 50 peopleCloudflare's daily free plan limitsBuilt inCloudflare runs the machines
Your own serverdocker compose up -d, about 15 minutesWhat your server costsYour server's memory, CPU and disk. One server, no failoverNeed a free Cloudflare tokenYou: system updates, firewall, disk

Worth knowing.

  • Your own server is a newer way to run Yakyard, with fewer teams on it. It runs on Wrangler's local mode, which Cloudflare built for development.
  • One server, no automatic scaling and no failover. If the server is down, so is your chat. Size it for your team and keep backups somewhere else.
  • You look after the server: operating system updates, the firewall, disk space and Docker.
  • Transcripts need a Cloudflare token, and the audio goes to Cloudflare to be transcribed. Voice notes sent while transcripts were off stay without one.
  • People in your workspace can read what isn't locked, and so can anyone who gets into the server or its backups.
  • Locked conversations are still a preview. The encryption library is audited. Yakyard's own code around it isn't yet.
  • npm run backup and the automatic updates are for Cloudflare installs. On your own server, use the two scripts. There's no guide yet for moving an existing Cloudflare install over.
  • The database doesn't change in this release.

Update.

Back up first, then update. Nothing to turn on afterwards.

On Cloudflare:

npm run backup
npm run update

On your own server:

sh docker/backup.sh
git pull
docker compose pull
docker compose up -d

New to Yakyard? Setup on Cloudflare takes about 30 minutes, no coding.