Deploy OpenTodo

Local-first task manager with CalDAV, REST API and mobile apps

Deploy OpenTodo

Just deployed

/data

Deploy and Host self hosted OpenTodo on Railway

This template deploys OpenTodo, a free and open-source local-first task manager, as one service on Railway with a persistent volume for its SQLite database.

About Hosting OpenTodo open-source software on Railway (self hosted OpenTodo template)

OpenTodo is free, AGPL-3.0 licensed software, and this template runs it on Railway so the data stays in a volume you control.

This is independent community packaging of OpenTodoApp/OpenTodo v1.5.0. It is not affiliated with or endorsed by OpenTodo.

Why Deploy OpenTodo, the self-hosted local-first task manager on Railway

A hosted task app keeps your list on someone else's server and charges a subscription indefinitely.

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying OpenTodo on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

Railway vs Other Hosting Providers and VPS for OpenTodo self hosting

Railway handles the container, HTTPS domain, and volume for you, while a general provider leaves more setup to you.

ProviderWhat You Get with RailwayWhat You Get with the Other Provider
DigitalOceanA one-click template with a public HTTPS domain, a /data volume, and a /healthz check.A droplet where you install Docker, run the container, and set up a reverse proxy and TLS.
AWSThe same template setup without writing networking or IAM policies.Broad control over compute, storage, and networking, with more services to configure.
HetznerManaged deployment from the template, with domain, volume, and restarts handled for you.Low-cost servers where you handle OS updates, Docker, backups, and HTTPS yourself.

Choose Railway for a faster setup, and a VPS if you need full control over the host.

Common Use Cases for hosted OpenTodo

  • Personal task list with your own data: Keep a single task list on a Railway volume, where the SQLite database, attachments and backups all sit under /data that you control.
  • Syncing with CalDAV clients: Point a CalDAV-capable calendar or task client at your deployed URL so tasks stay in step with the tools you already use.
  • Automating tasks through the REST API: Create and update tasks from scripts, cron jobs or other services that call the API, with changes showing up in the app right away.
  • Using the iOS and Android apps: Connect the mobile apps to the same public HTTPS address so you can add and check off tasks from your phone.
  • Importing from another task app: Bring existing tasks across from a previous task app through the optional import feature, then run OpenTodo as your single source of truth.

Dependencies for OpenTodo Docker hosted on Railway

This template deploys one public service on port 8080 with a volume at /data, health check /healthz (timeout 120 seconds), and restart policy Always. Keep one replica. There are zero deploy-time inputs.

Deployment Dependencies for Managed OpenTodo Service

The service listens on port 8080 behind a public HTTPS domain. A volume at /data holds the SQLite database, attachments and backups. The health check is /healthz with a 120 second timeout, and the restart policy is Always. Keep one replica, because that volume holds the instance state.

Implementation Details for OpenTodo

The image is ghcr.io/onepush-dev/opentodo:1.5.0, the unmodified upstream ghcr.io/opentodoapp/opentodo:1.5.0 app, with USER 0 added so the process can write the root-owned Railway volume at /data (the upstream distroless image runs as uid 65532). There is no start wrapper. Baked values are OPENTODO_ADDR=:8080, OPENTODO_DATA_DIR=/data and OPENTODO_ALLOW_SIGNUP=false.

Two template variables are generated or referenced, with no inputs:

  • OPENTODO_BASE_URL defaults to the Railway HTTPS domain. Passkeys and cookies are bound to it; change it if you add a custom domain.
  • OPENTODO_SETUP_TOKEN is the secret asked once when you create the owner account. Registering without it fails, and after the owner exists sign-up stays closed unless you set OPENTODO_ALLOW_SIGNUP=true.

Optional OPENTODO_* settings for SMTP, OIDC, S3 or WebDAV backups, and email-to-task are not pre-set.

How does OpenTodo compare against other tools

OpenTodo vs a hosted task app (Hosted Task App Alternative)

  • Where you keep your data: OpenTodo stores everything in one SQLite database on a volume you control, so your task list lives on infrastructure you chose rather than a vendor's servers.
  • Sync and clients: OpenTodo syncs through CalDAV, a REST API and its own iOS and Android apps, and it works offline on each device. A hosted app may offer a more polished out-of-the-box experience with less setup.
  • Cost model: You pay for the Railway resources the service uses, and the software itself is AGPL-3.0 open source. Hosted apps usually bill a subscription, though their free tiers may suit light use well.

OpenTodo vs a local single-binary install (Local Binary Alternative)

  • Always-on access: Running the Railway template gives you a public HTTPS address that phones and CalDAV clients can reach at any time, while a local binary is only reachable on the machine running it.
  • Setup and upgrades: A local binary needs you to manage the process, backups and updates yourself. The template handles the container and health checks, though you still own your data and backups.
  • Simplicity: A single local binary on a laptop is the lightest option and needs no hosting account. It is a better fit if you only ever use one computer.

OpenTodo with Docker vs Railway (Docker on Railway Alternative)

  • Control: Running the Docker image on your own VPS gives you full control over the host, networking and reverse proxy. Railway trades some of that control for a guided deploy with a generated setup token and a public domain.
  • Volume handling: The template runs the unmodified app as root so the Railway volume is writable, which is a deliberate choice you should know about. On your own Docker host you can mount volumes with your preferred permissions instead.
  • Scaling: Keep one replica, because the SQLite database and attachments live on a single local volume. Multiple replicas would not share that state safely.

How to use OpenTodo on Railway?

Follow these steps on your first day after the deploy finishes.

1. Open the public domain that Railway generated for your OpenTodo service.
2. The setup screen asks for a setup token. Copy OPENTODO_SETUP_TOKEN from the Variables tab, paste it in, then choose an email and password. That account becomes the owner.
3. Sign-up stays closed. Invite other people from Settings, or set OPENTODO_ALLOW_SIGNUP=true only if you want open registration.
4. Connect iOS, Android or any CalDAV client to the same URL you opened in step 1.
5. If you add a custom domain, update OPENTODO_BASE_URL to match it.
6. Keep one replica. The app stores its SQLite data on a single volume at /data.
7. Railway checks /healthz to decide whether the service is healthy.

How to self host OpenTodo on other VPS Services (OpenTodo self hosting guide)

Clone the Repository

Clone the upstream project so you have its files and README for reference:

git clone https://github.com/OpenTodoApp/OpenTodo.git
cd OpenTodo

Install Dependencies

You can run OpenTodo as the upstream container image or as the single Go binary. The container route needs only Docker.

Configure Environment Variables

Nothing is required to start. Every setting is an optional environment variable with a safe default, and the upstream configuration reference lists them.

Start the OpenTodo Application

Run the container with a data volume and the documented port:

docker run -d -p 8080:8080 -v opentodo-data:/data ghcr.io/opentodoapp/opentodo:stable

Open your-domain in a browser, paste the setup token, then choose an email and password to become the owner. Put HTTPS in front of it before you expose it to the internet.

Pricing and License of OpenTodo (OpenTodo pricing)

OpenTodo is free and open-source software licensed under AGPL-3.0.

Your costs come from the infrastructure you run it on, such as Railway usage or a VPS, plus any model or mail provider you choose to connect.

OpenTodo hosted vs self hosted comparison (Pricing, features, costs, and more)

This template packages the AGPL-3.0 software. The upstream project also describes a hosted option, but that offering is not used or included here.

Monthly cost of self hosting OpenTodo on Railway

Railway bills on usage, so the monthly cost depends on the RAM and CPU the OpenTodo service uses, the size of the /data volume, and any other services in the same project.

System Requirements for Hosting OpenTodo on a VPS

A VPS needs a Linux host that can run a container or the single Go binary, persistent disk for the data directory, and HTTPS in front of it if you expose it publicly.

Frequently Asked Questions (FAQs)

How do I become the owner of my OpenTodo instance?

Open your Railway domain and paste the OPENTODO_SETUP_TOKEN value from the Variables tab when the setup screen asks for it.

Can a stranger claim my URL before I do?

No.

How do I use a custom domain?

Add the domain in Railway, then change OPENTODO_BASE_URL to that address. Passkeys and cookies are bound to this URL, so keep it accurate.

Do I need SMTP to run OpenTodo?

No. SMTP is optional, and the app runs without it. You can add it later through the optional OPENTODO_* settings.

What should I back up?

Back up the /data volume, which holds the SQLite database, attachments and backups.


Template Content

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
51
View Template
Foundry Virtual Tabletop
Self-hosted virtual tabletop for role-playing games (license required)

Lucas
71
View Template
Letta Code Remote
Run a Letta Code agent 24/7. No inbound ports, just deploy.

Letta
52