Productivity made simple

The application is open source under the MIT licence, so you can run it on your own server for nothing, modify it, and build on it without paying anyone. There are no seat counts and no features held back: the self-hosted build is the whole product. tududi Cloud is a paid service, because hosting, backups and email cost money to run. You are paying for the operating work, never for access to the software.

Yes, and you do not need to buy anything first. The MIT licence permits commercial use, including inside a business and inside a commercial product, with no revenue threshold and nothing to report. If your finance team needs an invoice, a Cloud subscription is billed through our payment provider and produces one. Nothing on this page sells permission, because permission is already yours.

Yes. It is built primarily by one maintainer, with contributions from the community, and it ships often. Every release is listed on the GitHub releases page, linked from the Changelog in the menu above, so you can judge the pace yourself rather than take our word for it. Development happens in the open: issues, a public roadmap, and a Discord where questions get answered.

The app is MIT licensed and the source is public, so it cannot be withdrawn from you. Anyone can keep running it, and you can fork it. On tududi Cloud your data lives in a standard tududi database rather than a proprietary format, so if the service ever shut down you would get your data and a guide to moving it onto your own server.

No. Cloud is €5 a month or €50 a year, and that is the whole price list: no free tier, no trial clock, no card taken for something that quietly starts billing later. There is a 30-day money-back guarantee if it turns out not to suit you, and there is a live demo on this page if you would like a look around first. The free way to use tududi is to run it on your own server, which is the same application.

You are paying to not run infrastructure. tududi Cloud gives you the same system with the server, updates, backups and email handled for you, which is the fiddly, unglamorous half of self-hosting. Cloud is the path we recommend. Self-hosting is the better deal only if you already run Docker and a reverse proxy and actively want to operate the stack.

No. Both AI layers are off until you switch them on, and tududi is a complete system without either. If you never enable them, nothing is missing and nothing nags you.

That depends which of the two layers you mean, and the difference matters. The MCP server runs inside your own instance: an agent such as Claude Desktop connects to that instance directly, so the conversation is between your agent and your own tududi rather than a broker in between. The AI Assistant is different. It calls an OpenAI-compatible provider, so if you point it at a hosted one, the contents of those requests go to that provider. Point it at a local model instead, such as Ollama or LM Studio, and nothing leaves your machine. It stays off until you supply a key, so this is always your choice rather than a default.

MCP is the Model Context Protocol, an open standard for connecting AI agents to real systems. tududi ships an MCP server exposing 59 tools spanning tasks, projects, areas, goals, habits, notes, people, tags, views, inbox, search and metrics, so an agent can capture, find, update and finish work rather than just talk about it. It is opt-in, it comes with Cloud and with every self-hosted instance, and it works with Claude Desktop, Cursor, Windsurf, Cline, or any other MCP client.

Yes, at any time. Export everything as a single file from your profile and import it into a self-hosted tududi, which reads the same format. Deleting your account removes your data, attachments and backups from our servers and cancels any subscription.

Docker, somewhere persistent to store the database, a reverse proxy with TLS in front of it, and the discipline to apply updates and keep backups. It is comfortable on a small VPS or a machine on your own network, and the commands are in the Self-Host section and the docs. Most people are better served by Cloud, which is the same application with none of that work.

Everything lives in a single SQLite database file inside the volume you mounted. Backing it up is copying that file somewhere safe, and restoring it is copying it back. tududi also snapshots the database automatically before it applies migrations, keeping recent copies. There is no proprietary format and no export step standing between you and your own data.

Yes. A single instance can host multiple users, and projects can be shared with read-only or read-write access, which the tasks and notes inside them inherit. Self-registration is off by default, so an admin either creates accounts or deliberately opens sign-ups. Nobody gets in because you forgot to close a door.

tududi installs as a PWA rather than a native app. Add it to your home screen on Android or iOS, or install it on a desktop, and it behaves like an app: it reads from cache when you are offline and syncs your changes when you reconnect. There is nothing to download from the App Store or Play Store.

Yes, and that is the normal way to run it. Set TUDUDI_TRUST_PROXY so the app trusts the forwarded headers from nginx, Caddy, or Traefik. If you skip it, logins and IP logging behave strangely in ways that are hard to diagnose, so the app raises a specific error rather than failing quietly. The accepted values are documented in the README.