Yarukoto
One container, one SQLite file. Apps for iPhone, Android, the Mac and Windows, shared lists for everyone at home, and your to-dos right inside Home Assistant.
Your data never leaves your server.
A todo app lives in the gaps of your day: a lock screen, a menu bar, a glance between meetings. So Yarukoto uses each platform's own controls instead of drawing look-alikes, and it ships as a real app on each one. The web app is there too, served by your server, but it isn't the thing wrapped up and called an app.
The same app as your phone, in a window of its own, with the wide layout and keyboard shortcuts. Connect it to your server, or explore with sample data first.
The Windows installer isn't signed yet, so the first time it runs Windows asks you to choose More info, then Run anyway. Every version is on the releases page.
Everyone gets their own account, their own Inbox, tags, folders and saved filters. Lists start private; share one and everyone at home can see and edit it. The groceries are shared, your work list stays yours.
Signing in is a QR code, in whichever direction has a camera. Every QR also shows a short code you can type, for the devices that don't.
The Yarukoto integration turns the lists you pick into Home Assistant to-do lists. Tick off the groceries from a wall tablet, add to them by voice, or build an automation around what's due today.
#chores this week, ready to be ticked off.github.com/wyne/yarukoto-home-assistant as a custom repository and install Yarukoto.
The due date and time, the #tag, the !priority and the ~list come out of one line. Anything unrecognized stays as the title, and the chips show you what was understood before you commit.
every mon, wed, every 2 weeks, or every! 3 days to count from when it's done.Every pane is a stop on Tab, the arrows move inside it, and Esc always lands you back on the list. Add a task, file it, open the next one and check off the last, without touching the trackpad.
The same tasks, cut the way you think about them. Every view is a real link, so the one you live in is a bookmark away.
The server speaks the Model Context Protocol at /mcp, so any assistant or agent that supports MCP can list, add, schedule and complete your tasks. It sees exactly what your account sees, and “friday” means friday in your time zone, not the container's.
# add to any MCP client URL https://todo.example.com/mcp Auth Bearer $YARUKOTO_TOKEN # then just ask › what's due on the house list?
One container, ghcr.io/wyne/yarukoto, built for amd64 and arm64. Your tasks live in a single SQLite file in the folder you mount, and survive every update.
compose.yaml in it. Set YARUKOTO_TZ to your time zone.http://<server>:8080.Portainer, Dockge and Unraid's Compose Manager take the same file. To update: docker compose pull && docker compose up -d.
services:
yarukoto:
image: ghcr.io/wyne/yarukoto:latest
restart: unless-stopped
ports:
- "8080:8080"
environment:
YARUKOTO_TOKEN: ${YARUKOTO_TOKEN:?set a token in .env}
YARUKOTO_TZ: America/New_York # your time zone
volumes:
- ./data:/data
echo "YARUKOTO_TOKEN=$(openssl rand -hex 32)" > .env docker compose up -d
http://<server>:8080.To update: docker pull the image, then remove and re-run the container with the same flags. The data folder is untouched.
export YARUKOTO_TOKEN=$(openssl rand -hex 32)
echo "$YARUKOTO_TOKEN" # save this
docker run -d --name yarukoto --restart unless-stopped \
-p 8080:8080 \
-v "$PWD/yarukoto-data:/data" \
-e YARUKOTO_TOKEN \
-e YARUKOTO_TZ=America/New_York \
ghcr.io/wyne/yarukoto:latest
docker/yarukoto/data.openssl rand -hex 32, fix the volume path if your data isn't on volume1, and set PUID/PGID to your DSM user's ids (id over SSH prints them). Start the project.http://<nas-ip>:8080. If another package already has 8080, change only the left side of the port.It pulls the prebuilt image, so the NAS never compiles anything. The NAS won't notice new versions on its own; to update, over SSH: sudo docker compose pull && sudo docker compose up -d.
services:
yarukoto:
image: ghcr.io/wyne/yarukoto:latest
restart: unless-stopped
ports:
- "8080:8080"
environment:
YARUKOTO_TOKEN: CHANGE_ME_RUN_openssl_rand_hex_32
YARUKOTO_TZ: America/New_York
PORT: 8080
DATABASE_PATH: /data/yarukoto.db
PUID: 1026 # your DSM user's id
PGID: 100
volumes:
- /volume1/docker/yarukoto/data:/data
docker-compose.build.yml to its compose file builds the server and web app from your checkout instead of pulling the image.http://localhost:8080.To update: git pull, then the same up command. Building needs a few minutes and more memory than a NAS usually has, so use the prebuilt image there.
git clone https://github.com/wyne/yarukoto.git cd yarukoto echo "YARUKOTO_TOKEN=$(openssl rand -hex 32)" > .env echo "YARUKOTO_TZ=America/New_York" >> .env docker compose -f docker-compose.yml -f docker-compose.build.yml up -d --build
Open the server in a browser or the app and use the token once. That account is the household's admin.
Settings → Household → New person shows a QR. Each phone scans it and is signed in. No more tokens.
Fine as plain HTTP at home. Before it faces the internet, put Caddy, Traefik or your NAS's reverse proxy in front.
The server writes a snapshot to data/backups every day and keeps the newest seven. Point Restic, Hyper Backup or whatever you use at that folder. More on backups.
The installation guide covers each route in full, and every setting, like trash retention and history depth, is in the configuration reference.
| Yarukoto | Hosted service | |
|---|---|---|
| Where the data lives | One SQLite file you can copy | Someone else's database |
| Cost | A container on hardware you own | Per month, per person, per tier |
| Signing in | Scan a QR, no passwords | Email, password, session |
| Your smart home | Local Home Assistant integration | A cloud integration, if any |
| Offline | UI never waits on the network | Varies; often read-only |
| If it shuts down | It doesn't — you're running it | Export and start over |
Many self-hosted task managers are built around the browser. Yarukoto treats iOS and Android as first-class clients, with offline edits that queue locally and sync when your server is reachable again.
Sample data mode runs the whole app client-side — no server needed. Everything stays on the device and resets when you reload.