Tududi Hosting

How Tududi works

Tududi organises work through a hierarchy of areas, projects, tasks, subtasks, notes, and tags. Due dates, priorities, filters, recurring patterns, and completion-based scheduling help separate immediate work from recurring routines and longer projects. Notes can attach context to a project, while areas group related projects around responsibilities such as work, home, health, or learning.

Upstream Tududi also documents project sharing, a progressive web application, API keys, OIDC, CalDAV, Telegram capture, and multiple languages. The catalogue template creates one administrator account and persists its database and upload directories. It does not configure an identity provider, Telegram bot, CalDAV client, external collaboration policy, or any third-party integration on the user’s behalf.

Key Tududi features

Recurring tasks support several schedule patterns, optional completion-based recurrence, custom intervals, and end dates. Subtasks expose progress within a larger item, while Today, Upcoming, Someday, and other filters help focus the working view. Correct recurrence still depends on the selected timezone, due dates, and the operator’s interpretation of an intended routine.

API and integration capabilities require separate credentials and security review. Application email is disabled across the hosted service, so email-based invitations, recovery, notifications, or delivery should not be assumed. The generated administrator email is an account identifier; it does not mean an inbox or outbound mail service is included.

Tududi vs Todoist

Tududi combines tasks with areas, projects, notes, tags, recurring logic, and self-hosted integrations. Todoist supplies a provider-operated service with natural-language task entry, recurring due dates, reminders, many integrations, apps across desktop and mobile platforms, list, calendar, and board views, and shared team workspaces.

Todoist may suit people who want polished native clients, a large integration catalogue, provider-maintained synchronisation, and managed team permissions. Tududi is attractive when the data and server address should remain under the operator’s control and its broader life-management structure matches the workflow. The hosted package does not recreate Todoist’s account network or app ecosystem.

Who uses Tududi

Individuals can plan household and professional responsibilities, freelancers can connect tasks to projects and notes, and small teams can share selected projects. Habitual work, monthly administration, and multi-step outcomes benefit from subtasks and recurring patterns, while tags create views that cross project boundaries.

Tududi is not an enterprise portfolio platform, payroll system, legal reminder service, calendar provider, identity provider, or substitute for professional project governance. Users should test offline queues, CalDAV behaviour, API clients, recurrence rules, and collaboration permissions before adopting them for critical deadlines.

Self-hosting Tududi: requirements and cost

Tududi resource demand grows with users, projects, tasks, notes, uploads, recurrence generation, API traffic, collaboration, and integrations. PostgreSQL and MariaDB are Not required in the catalogue; the local database and uploads are persisted by the template. The software adds no separate application fee, while a small team should watch upload growth and busy API or synchronisation workloads.

On AvaHost, Tududi uses Plan 1 at €2. The hosted Tududi package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. One generated administrator account is included. Application email is disabled, and the package does not configure OIDC, Telegram, CalDAV clients, API consumers, app-store PWAs, invitation delivery, or recovery mail. Administrators must review sharing and disable unused registration or integration paths where the application permits.