Portainer Templates logo

Portainer Templates

OpenTodo OpenTodo

Container

Productivity

Open-source, local-first task manager. Works offline and syncs every device from one small container. Source: https://github.com/OpenTodoApp/OpenTodo

Image details

Architecture: amd64, arm64
Image size: 17 MB
User: opentodoapp

Source details

Stars: 659
Forks: 66
Language: TypeScript
License: AGPL-3.0
Updated: 7 minutes ago
Website: open-todo.app/

Configuration

Type
Container
Platform
linux
Image
ghcr.io/opentodoapp/opentodo:stable
Ports
8080:8080/tcp
Volumes
/data
Env vars
OPENTODO_SETUP_TOKEN=OPENTODO_BASE_URL=OPENTODO_ALLOW_SIGNUP=falseOPENTODO_TRUSTED_PROXIES=
Restart
unless-stopped

Notes

Open http://<your-host>:8080 right after deploying: the first visitor creates the owner account (paste the setup token there if you set one), and sign-up is closed after that. Everything OpenTodo stores is in the /data volume, so back that volume up. On plain http, tasks, sync and sharing work; installing the app, offline use, push notifications and passkeys need https: put a reverse proxy with a certificate in front and set the public https address. Updates: re-pull the stable image (Recreate with Re-pull image). Docs: open-todo.app/docs/self-hosting/portainer

Standalone Install

Select an install method, to see config/commands for deploying OpenTodo

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select OpenTodo, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation, or see OpenTodoApp/OpenTodo for app-specific guidance.

OpenTodo logo


OpenTodo


Plan your day without renting your to-do list.


OpenTodo is a free, open-source to-do app you run on your own server or have hosted for you. It works on your phone and your computer, even offline, shares lists with your family or your team, and keeps your data with you.


Try the demo · Install · Docs · Website


5 minutes to help shape OpenTodo: take the anonymous survey


License: AGPL-3.0 CI Latest release Buy me a coffee Sponsor on GitHub Discord


Quick add in plain language with date, priority and project chips, a card moved across a project board, then a task added offline that syncs on reconnect


Download on the App Store


New: OpenTodo for iPhone and iPad is in the App Store. It's the first release, a first step: it connects to your OpenTodo server and adds reminders on the phone, the share sheet, a Today widget and Face ID unlock. Expect some rough edges; tell us what to improve.
Ways to run it: PikaPods (hosted, no server needed) · Docker · Umbrel (coming soon) · Unraid · Home Assistant · Kubernetes (Helm) · Single binary · iPhone and iPad app (App Store) · Android app (APK from GitHub; Google Play and F-Droid coming soon) · all 20 platforms

How it works

  1. Capture

Type a task the way you say it: Call Sarah next Wed 3pm #work p1 sets the date, time, project and priority. Dictate it, send a page from your phone's share menu or the browser extension (Chrome, Firefox), or forward an email. Anything without a home lands in the Inbox. Quick add · Voice · Capture
Quick add with a task typed in plain language and chips for its date, project and priority

  1. Plan your day

Today shows what is due and what is still open from earlier. Give tasks an estimate and drag them onto the Day or Week calendar to see whether the day fits. Today · Time blocking
The Day calendar with timed tasks as blocks sized by their estimate and the planned total against the day length

  1. Focus

Open one task in Focus and start a Pomodoro, Flowtime or countdown timer. The time is logged to the task. Focus
The Focus screen with one task, a large timer and buttons to pause, complete or take a break

  1. Share

Share a project with your family or your team as viewer, editor or admin. Assign tasks, comment, and see what changed. Everyone can edit offline. Sharing
The Share dialog for a project with an email field, a role menu and the member list

Highlights

  • Your data stays yours. Everything lives in one folder on your server. Export it at any time, import it anywhere, and schedule backups, encrypted if you like, to disk, S3 or WebDAV. Backups · Import and export
  • Works offline on every device. Each phone and computer keeps a full copy, so the app works with no connection and syncs when it's back. Install the app
  • Bring your tasks. Import from Todoist, TickTick, Things, Super Productivity, Microsoft To Do, Apple Reminders and more, with a preview and undo. Import
  • Private by design. No telemetry, no analytics, no third-party scripts. Turn on end-to-end encryption and the server holds only ciphertext. Privacy · Encryption
  • Bring your own AI, if you want it. Talk to an assistant in the app, or connect the one you already use. Off by default, and every change can be undone. AI

No subscription, no lock-in, no tracking.
Explore all features →

How it compares

OpenTodoTodoistTickTickThingsSuper Productivity
Open source✅❌❌❌✅
You can host it yourself✅❌❌❌✅
Works offline✅✅⚠️✅✅
Free, with every feature✅❌❌❌✅
No subscription✅❌❌✅✅
Optional end-to-end encryption✅❌❌❌✅
Shared projects✅✅✅❌❌

✅ yes · ❌ no · ⚠️ partly, or not documented. Todoist and TickTick have a free plan with limits; Things is a one-time purchase per device type. Based on each product's public information as of November 2026. If an entry is wrong, open an issue with a source.
Full comparisons →

Install

Try it in 30 seconds

  • No install: open the demo and press Try the demo. You get a private copy with sample data, deleted after a few hours.
  • On your machine or server:

```bash docker run -d -p 8080:8080 -v opentodo-data:/data ghcr.io/opentodoapp/opentodo:stable ```
Open . The first visit creates your account. No configuration needed.

Docker Compose

git clone https://github.com/OpenTodoApp/OpenTodo.git
cd OpenTodo
docker compose up -d

Data is kept in the opentodo-data volume. On a server reachable from the internet, finish setup right after starting it, or set OPENTODO_SETUP_CODE=required (the setup code
). Behind a reverse proxy, set OPENTODO_BASE_URL=https://todo.example.com.
The image is published for linux/amd64 and linux/arm64. :stable is the latest release, :1 follows every 1.x release, a minor tag such as :1.5 gets that line's fixes only, a full version such as :1.5.0 pins one release, and :latest follows the main branch. Upgrades from any release since 0.1.0 work directly, and nothing you rely on breaks within 1.x (stability). More in Running with Docker.

Single binary

Download opentodo-<os>-<arch> for Linux, macOS or Windows from the latest release and run it. It serves on port 8080 and keeps its data in ./data. To build from source: make build && ./bin/opentodo (Go 1.27+ and Node 22+).
Managed hosting: PikaPods, Railway. These links support the project: OpenTodo receives a share when you host through them.

Configuration

Nothing is required. Every setting is an optional environment variable with a safe default: see the configuration reference. To add people, keep sign-up closed and send invitation links (managing users).
The self-hosting handbook covers every platform, TLS, backups, upgrades and monitoring. The ot command-line client is in the CLI guide.

Privacy

The app talks only to your own server: no analytics, crash reporters, update pings or third-party fonts. Two things are on by default and can be turned off: maps for task locations, fetched through your server with no account data, and web push to the service each phone's browser chose. Everything else the server contacts, such as webhooks, backup destinations, single sign-on, email or an AI provider, is something you set up. The audit log never records task content (what is logged).

Documentation

Read the docs with screenshots and search at open-todo.app/docs, or in the app under Help. The same pages are in docs/.

Build your own client

Every server describes its API at /api/v1/openapi.json (OpenAPI 3.1, generated from the code, stable through 1.x). Point a generator at it and you have a typed client:
curl -s https://todo.example.com/api/v1/openapi.json -o openapi.json
npx openapi-typescript openapi.json -o opentodo.d.ts

The same file is docs/openapi.json and an asset of every release. Sign in with an API token from Settings → Integrations → API tokens; the API guide has the details, and ot, the Obsidian plugin and the n8n nodes are clients built on it.
Under the hood
┌───────────────────────── device ─────────────────────────┐      ┌──────────── server ────────────┐
│ React PWA  ──►  IndexedDB (source of truth)              │      │ Go binary + SQLite             │
│                 │ every edit = field ops {ts, device}    │ sync │  ops log (append-only)         │
│                 └► outbox ──────────────────────────────►├─────►│  fields (last-writer-wins)     │
│                 ◄─ ops from other devices ◄──────────────┤◄─────┤  REST, CalDAV, email, import   │
└──────────────────────────────────────────────────────────┘      │  all write through ops         │
                                                                  └────────────────────────────────┘

  • Every change is a small operation that sets one field of one entity, stamped with a hybrid logical clock and the device id.
  • Devices apply changes locally first, then sync. The same per-field rule runs everywhere, so all devices agree no matter the order. Notes merge character by character.
  • The REST API, CalDAV, email and imports write through the same log, so a task created with curl shows up on your phone right away.
  • One Go binary with the web app inside and a single SQLite file. It idles at about 20 MB of memory and runs on a Raspberry Pi.

More in architecture and the sync protocol.

Help without coding

  1. Star and share. A star on GitHub helps other people find OpenTodo.
  2. Leave feedback in Discussions or on Discord.
  3. Report bugs in issues.
  4. Review a translation. The app speaks eleven languages; tell us where a word feels wrong (translating).
  5. Test it on your devices and report back in the call for testers.
  6. Answer questions from other people in Discussions and on Discord.
  7. Sponsor: buy me a coffee or GitHub Sponsors.

To contribute code, read CONTRIBUTING.md: changes that alter behaviour start as an OpenSpec change. Security issues go to the address in SECURITY.md.

Supporters

OpenTodo is free and always will be. If it helps you, you can buy a coffee or sponsor it; the support page says what it costs to run and where the money goes.
Thank you to everyone who keeps OpenTodo going. Supporters who want to be listed appear here.

Star History

<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=opentodoapp/opentodo&type=date&theme=dark&legend=bottom-right" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=opentodoapp/opentodo&type=date&legend=bottom-right" />
<img alt="Star History Chart" src="https://api.star-history.com/chart?repos=opentodoapp/opentodo&type=date&legend=bottom-right" />

License

AGPL-3.0-only. You can run, study, modify and share OpenTodo freely. If you offer a modified version as a network service, you must offer its source under the same license. That is what keeps a self-hosted project from being quietly turned back into a subscription.

Serve OpenTodo on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying opentodo.example.com to http://opentodo:8080

Add this to your Caddyfile

opentodo.example.com {
	reverse_proxy http://opentodo:8080
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs opentodo
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8080 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8080
  • Stop the other service, or pick a different host port. In 8080:8080 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8080. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, opentodo can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8080

Image won't pull

Test the pull directly on the host: docker pull ghcr.io/opentodoapp/opentodo:stable

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect opentodo --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Required settings are blank

OPENTODO_SETUP_TOKEN, OPENTODO_BASE_URL, OPENTODO_TRUSTED_PROXIES have no default value, and opentodo may crash or misbehave if left empty.

  • Fill them in on the deploy screen before hitting deploy.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

OpenTodo runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything OpenTodo needs bundled into one download. This template pulls ghcr.io/opentodoapp/opentodo:stable, which Docker fetches once (about 17 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. OpenTodo's comes from the GitHub Container Registry, published by opentodoapp.

Version tags

The bit after the colon in the image name is the version tag. This one pins stable, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 8080:8080 means it's reachable on port 8080 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8080 in a browser. It opens:

  • 8080:8080, likely the web interface

Volumes

A volume is where OpenTodo keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /data as a volume Docker manages for you

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. OpenTodo takes 4 of them, and 3 need a value before it'll start properly:

  • OPENTODO_SETUP_TOKEN, needs a value. When set, creating the first (owner) account asks for this token, so a server others can reach cannot be claimed by a stranger. Generate one with: openssl rand -hex 16
  • OPENTODO_BASE_URL, needs a value. The https address people open behind a reverse proxy, for example https://todo.example.com. Leave empty when you open OpenTodo by the server's address over plain http: an https value there breaks sign-in.
  • OPENTODO_ALLOW_SIGNUP, pick one of false, true. True lets anyone who can reach the server create an account. Otherwise the owner invites people.
  • OPENTODO_TRUSTED_PROXIES, needs a value. Reverse proxies whose X-Forwarded-For is trusted for the visitor's address: IP addresses or ranges such as 192.0.2.0/24 separated by commas, or cloudflare. Set it only when every request comes through them.

Restart policy

The restart policy here is unless-stopped, so Docker restarts OpenTodo after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so OpenTodo sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container opentodo. That's what you'll spot in the containers list and use in commands like docker logs opentodo.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

OpenTodo is open source, released under the AGPL-3.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set OpenTodo up. Add the template list to Portainer once, then deploying OpenTodo is a click rather than a wall of config.