Leantime: Project Management for Teams That Think in Goals, Not Tickets

Most project management software is built for software developers. The terminology, the workflows, the defaults: story points, sprint backlogs, ticket queues. If you run an agency, consult for clients, manage a small business, or lead a creative team, you are supposed to adapt that vocabulary to your work. Leantime takes a different approach. It organizes everything around goals and milestones rather than development tickets, and it includes the tools that non-technical teams actually use: time tracking, client portals, retrospectives, and an AI assistant that helps write project briefs. It has 11,199 stars on GitHub and is free to self-host under the AGPL-3.0 license (an open-source license that lets you run and modify the software freely, with the requirement that modifications you distribute also remain open-source).

What Leantime actually is

Leantime is an open-source project management platform built around lean startup concepts. Lean startup is a methodology that organizes work around goals, hypotheses, and learning cycles rather than a fixed output list. In practice, this means that in Leantime, you start a project by defining what success looks like, not by creating a backlog of tasks. The tasks and milestones are attached to those goals, not the other way around.

This is a meaningful design choice for agencies, consultants, designers, and small business teams. In Jira or a typical developer-oriented tool, the base unit is a ticket: a discrete unit of work assigned to someone. In Leantime, the base unit is closer to a project goal or milestone: an outcome you are working toward. Tasks exist inside that structure, not as a flat queue that grows indefinitely.

The tool covers the full project lifecycle for a small team: planning, task tracking, time logging, team reflection, and client-facing reporting. The AI assistant connects to OpenAI (or a self-hosted language model via Ollama, an open-source tool for running AI models on your own hardware) to help with the writing-heavy parts of project management: drafting goal statements, describing milestones, and summarizing project status for stakeholders.

What you get after installing it

Projects and goals are the organizing structure. Each project in Leantime is tied to a goal statement. Within a project, you create milestones (major checkpoints with due dates), and tasks live inside milestones. This hierarchy keeps work grounded in outcomes. You can also track a hypothesis for each project, in the lean startup sense: what you believe this project will accomplish, and how you will know it worked.

To-do lists and task views let you manage the day-to-day work. Tasks can be viewed in a list, on a Kanban board, or on a Gantt chart. A Kanban board (a term from Japanese manufacturing, meaning "signboard") is a visual task management method where tasks move across columns representing stages of work, typically something like To Do, In Progress, and Done. A Gantt chart is a horizontal bar chart where each task appears as a bar spanning its start and end date, showing what work is happening when and which tasks depend on others. Both views update in real time and give different members of the team the format that works best for them.

Time tracking is built directly into tasks. Team members log hours against specific tasks, not just against a project. This means at the end of an engagement you have an accurate breakdown of where the time actually went, which is useful for billing clients, pricing future work, and understanding where projects go over budget.

Retrospectives are structured team reflection sessions included as a first-class feature. A retrospective is a meeting format, popularized by Agile project management, where a team reviews a completed phase of work and answers three questions: what went well, what did not go well, and what to change next time. Leantime provides a dedicated retrospective module with structured prompts and a space to capture team responses, so the session produces a documented record rather than notes scattered across a chat log.

Ideation gives teams a place to capture and vote on ideas before they become tasks. This is useful for brainstorming phases where you want to collect suggestions from everyone on the team without immediately committing them to a project plan.

The AI assistant connects to OpenAI's API (application programming interface, the standard way software talks to an external service) or to Ollama for self-hosted AI. It can generate goal statements for a new project, write milestone descriptions, and produce project status summaries. These are the tasks that tend to create bottlenecks when project managers are context-switching between client calls and delivery work. The assistant does not replace the PM; it reduces the writing overhead of keeping project documentation current.

The client portal lets you share project views with clients without giving them full access. Clients can see progress on deliverables, review milestones, and check project status without logging into your internal workspace.

Reports aggregate time spent per project, task completion rates, and milestone progress. These reports are generated from your own data on your own server.

The install experience

The recommended install path is Docker Compose. Docker is software that packages applications so they run identically on any compatible server. Docker Compose is a configuration format that defines multiple containers and their connections in a single text file, then starts them all with one command. Leantime publishes an official compose file that sets up the application and its MySQL database (the relational database that stores your project data).

The realistic sequence for a first install on a home server or a rented VPS (virtual private server, a rented slice of a remote machine you access over the internet):

1. Install Docker and Docker Compose on your server.
2. Download Leantime's official Docker Compose file and the matching environment file from the repository.
3. Set a few required values in the environment file: the database credentials, the application URL, and a session secret.
4. Run docker compose up -d to start the containers.
5. Open the URL in a browser to complete the setup wizard and create your administrator account.

Someone familiar with Docker can finish this in under 30 minutes. A first-time Docker user should budget 60 to 90 minutes and read the documentation on leantime.io before starting. The documentation covers the compose setup in detail, and the GitHub Discussions section is active.

If you do not want to manage a server, Leantime GmbH offers Leantime Cloud at around 25 euros per month for small teams. This gives you a managed instance with no server maintenance. This article covers the self-hosted version, but the feature set is identical.

Where it fits and what to compare it to

Asana ($10.99 per user per month) is the most direct comparison for non-technical teams. Asana is polished, has a strong mobile app, and integrates with nearly every business tool. It is cloud-only, so your project data lives on Asana's servers. If you want a tool with no server management, a large app ecosystem, and a budget for a software-as-a-service subscription (a cloud product billed monthly per user), Asana is the right choice. Leantime makes sense when you want to own your data, control the hosting environment, or avoid recurring per-seat costs as the team grows.

Jira ($7.75 per user per month) is built for software development teams. It uses developer-centric concepts like sprints, story points, and backlogs. It can be configured for non-technical workflows but requires significant setup and usually needs someone who knows the tool well to maintain it. For a creative agency or small business team, Jira is nearly always overkill.

Trello (free tier available, owned by Atlassian) is a Kanban-only tool. It is easy to start with, which is its primary advantage. The free tier limits you to ten boards per workspace and does not include timeline views, time tracking, retrospectives, or goal tracking. Trello works well for simple task management and breaks down as projects get more complex.

ClickUp offers a very large feature set that can overwhelm non-technical teams. If you have never managed a team with ClickUp, the setup and configuration time is significant. Leantime is narrower in scope and more opinionated about how projects should be structured, which is either a limitation or a feature depending on how much flexibility your team needs.

Planka (covered separately on this site) is a simpler Kanban-focused alternative similar to Trello. It has no time tracking, no retrospectives, no goal structure, and no AI assistant. Planka is the right choice if all you need is a lightweight board tool and Leantime's structure would get in the way.

Verdict

Leantime is a good fit for agencies, consultants, and small business teams that want project management built around outcomes, not ticket queues. The combination of goal tracking, Kanban and Gantt views, time logging, and structured retrospectives covers most of what a small team needs to manage client work. The client portal and AI assistant address two specific problems that come up constantly in agency and consulting work: sharing progress with clients without giving them system access, and reducing the writing overhead of keeping project documentation current.

The caveats are worth stating plainly. The install requires Docker and a server or willingness to pay for Leantime Cloud. The lean startup framing is a genuine design choice, not just cosmetic, and teams that prefer a flat task list or a simple Kanban board may find the goal-and-milestone structure more rigid than useful. If you just need a Kanban board, Planka is the lighter starting point. If you need deep integration with a software development workflow, Jira is the better tool regardless of cost.

Leantime earns its 11,000-plus stars because it solves a real problem: project management for teams that think in goals and deliverables, not code commits and sprint backlogs. If that matches how your team works, the self-hosted version is free to run and worth evaluating before committing to an Asana subscription.