Open-source project management, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

What it is: Open-source (AGPL-3.0) project management platform targeting agencies and professional services teams — think Asana or Monday.com, but running on your own server [3].
Who it’s for: Agencies, consultancies, and small product teams that need time tracking, budget monitoring, and client visibility in one tool without per-seat pricing scaling out of control [website].
Cost savings: Asana Premium runs ~$10.99/user/month; Monday.com Standard is ~$12/user/month. Worklenz Cloud is ~$6/user/month [3]. Self-hosted on a $6 VPS collapses to near zero for any team size.
Key strength: Unusually complete feature set for an early-stage open-source project: time tracking, financial insights, resource planning, Gantt, Kanban, client portal, and project templates all in one install [website][3].
Key warning: AGPL-3.0, not MIT — if you embed Worklenz in a product you sell, you must open-source that product or negotiate a commercial license. The cloud free tier also has real limits (5 members, 3 projects, 1 GB storage) that the homepage doesn’t make obvious [1][website].

What is Worklenz

Worklenz is an all-in-one project management platform aimed at agencies and teams that currently manage projects across spreadsheets, Trello, and three different SaaS tools. The pitch is consolidation: time tracking, budget tracking, resource planning, and client communication in a single self-hostable install [website].

The project is based in Sri Lanka, licensed under AGPL-3.0, and as of this writing has 2,990 GitHub stars. Version 2.0 was a significant release — the team switched the frontend from Angular to React, redesigned the Kanban board with user-defined columns, added dark mode, and introduced recurring tasks [3]. That kind of architectural rewrite in a single version is either a sign of healthy engineering ambition or a warning that the codebase is still in flux, depending on your risk tolerance.

The GitHub description — “All in one project management tool for efficient teams” — is accurate and unusually honest. The website positions it more specifically toward agencies: profitability tracking, client portals, billable hour capture. Those are genuinely differentiated features compared to what you get in a basic Kanban tool [website].

One thing to get clear upfront: the homepage says “free forever plan available” but the free plan refers to the cloud tier, which OpenProject’s comparison page documents as limited to 5 members, 3 projects, and 1 GB of storage [1]. If you’re self-hosting via Docker under AGPL, those cloud-tier restrictions don’t apply — you run the full software on your own infrastructure. That distinction matters, and it’s buried.

Why people choose it

The testimonials on the Worklenz homepage are from agency founders and project managers who explicitly mention replacing Trello: “The boards is better than Trello… you can view % of tasks completed and also the roadmap is more attractive than others.” [website]. Another calls it “amazing product which is very simple and easy to use” and highlights time tracking and analytics as the deciding factors.

The Heise.de coverage of the 2.0 release [3] frames it as a direct alternative to Jira and Trello in the headline, which is the right framing for the self-hosted angle. The reason someone reaches for Worklenz specifically rather than a dozen other open-source PM tools usually comes down to one of three things:

Agency-specific financial tooling. Most open-source project management tools handle tasks well. Very few handle the question “is this client actually profitable?” out of the box. Worklenz surfaces burn rate, budget vs. actual costs, and billable hour tracking in a way that matters specifically to service businesses — not just software teams tracking sprints [website][3].

Resource planning. The resource scheduler shows team capacity on a single screen and lets you assign work based on skills and availability. OpenProject’s comparison [1] notes Worklenz doesn’t have meeting management or project wikis, but it does have the resource/capacity planning view that’s absent from lighter tools like Trello.

Self-hosted full control. The same argument that applies to any self-hosted tool: your client data doesn’t leave your server. For agencies handling sensitive client projects, that matters. One quoted user specifically calls out the portfolio view and roadmap visibility as reasons to switch [website].

What you don’t find in the reviews is any serious enthusiast community writing deep dives or migration guides. The project has under 3,000 GitHub stars and a Discord that’s active but small. Compare that to Plane (15,000+ stars) or OpenProject (10,000+ stars) and the community support layer is thinner.

Features

Based on the README, website, and the Heise 2.0 coverage:

Task and project management:

Task list view, Kanban board, Gantt chart timeline view [3][website]
User-defined Kanban columns to map actual workflow stages [3]
Task descriptions, comments, file attachments [3]
Subtasks [3]
Task dependencies [website]
Project templates — pre-built and custom [3][website]
Recurring tasks (added in 2.0) [3]
Task completion notifications to assigned team members [3]

Time and financial tracking:

One-click time logging directly on tasks [website]
Automatic analysis generation from tracked time [3]
Budget vs. actual cost monitoring [website]
Profitability tracking per client/project [website]
Billable hour capture (180K+ hours tracked across the user base) [website]

Resource planning:

Team capacity visualization [website]
Visual scheduler for workload distribution [3][website]
Utilization tracking across team members [website]
Allocation based on skills and bandwidth [website]

Reporting:

Real-time project health dashboards [website]
Team workload insights [website]
Analytics on team contributions [3]

Collaboration:

In-task comments [3]
Client portal (clients can view project progress without a full account) [website]
Dark mode (added in 2.0) [3]

What it’s missing compared to more mature tools: meeting management, project wikis, forums, team planner [1]. No mobile app yet — it was announced for an upcoming release as of the Heise article [3]. The REST API is listed as a feature in the GitHub metadata but isn’t prominently documented.

Pricing: SaaS vs self-hosted math

Worklenz Cloud:

Free tier: limited to 5 members, 3 projects, 1 GB storage [1]
Paid plan: approximately $6/user/month [3]
Enterprise: not publicly documented

Self-hosted (AGPL):

Software: $0
VPS: $6–15/month depending on team size and load
S3-compatible storage: MinIO self-hosted (free) or cloud object storage (~$2–5/month for typical usage)

Asana for comparison:

Free: up to 10 users, no timeline or reporting
Premium: ~$10.99/user/month
Business: ~$24.99/user/month (includes portfolios, goals, workload)

Monday.com for comparison:

Basic: ~$9/user/month (minimum 3 users)
Standard: ~$12/user/month
Pro: ~$19/user/month

Concrete savings math for a 10-person agency:

On Asana Premium: 10 users × $10.99 = $109.90/month ($1,319/year). On Monday.com Standard: 10 users × $12 = $120/month ($1,440/year). On Worklenz Cloud: 10 users × $6 = $60/month ($720/year). Self-hosted Worklenz on a $10/month VPS with MinIO: ~$12/month ($144/year, including S3 storage).

For a 10-person agency that genuinely uses the financial tracking and resource planning features, self-hosting Worklenz saves roughly $1,175–$1,295/year versus Asana Premium. The catch: you absorb setup time and maintenance, and AGPL means any internal modifications to the source stay internal, but you can’t sell a modified Worklenz as your own product without opening the source.

Deployment reality check

The Heise article [3] lists the technical requirements clearly: Node.js v18+, PostgreSQL v15+, S3-compatible object storage (MinIO or Azure Blob), Docker, and Docker Compose. The GitHub profile confirms docker and docker_compose as canonical deployment methods.

The S3 requirement is the wrinkle that most reviews understate. Unlike tools that store files on local disk, Worklenz requires an object storage backend from day one. If you don’t want to pay for AWS S3 or a managed equivalent, you’ll run MinIO alongside it — which is another service to manage. For a technical person, adding MinIO to a Docker Compose stack is a 10-minute addition. For a non-technical founder, it’s another thing that can break silently.

What you need:

A Linux VPS with at least 2–4 GB RAM (React frontend + Node.js API + PostgreSQL all running together)
Docker and docker-compose
Domain and reverse proxy (Caddy or nginx) for HTTPS
PostgreSQL v15+ (bundled or external)
Redis (bundled in Docker Compose)
S3-compatible storage — MinIO locally or any cloud provider

What can go sideways:

The 2.0 release migrated from Angular to React [3]. If you deployed the older version and are upgrading, verify the migration path in the release notes before running docker compose pull.
The Heise article notes mobile apps are “announced for upcoming releases” [3] — meaning you’re deploying a tool without a mobile client today.
AGPL-3.0 means the software is genuinely open-source, but if your team builds custom integrations into it, you need to be clear on the license obligations.
The OpenProject comparison notes Worklenz is based in Sri Lanka [1], which is relevant if you have clients with GDPR data residency requirements — you’d need to confirm where cloud-hosted data lives, or just self-host in an EU data center.

Realistic time estimate: 45–90 minutes for a technical user to a working self-hosted instance, including setting up MinIO. For a non-technical founder following documentation: half a day, or hire someone to do it once.

Pros and Cons

Pros

Genuinely complete feature set. Time tracking, financial insights, resource planning, Gantt, Kanban, client portal, and templates all included — not gated behind a paid tier on the self-hosted version [website][3].
Agency-specific financial tooling. Budget vs. actual monitoring and profitability per project are rare in open-source PM tools. For service businesses, this is the entire reason to consider it over Plane or OpenProject [website].
Client portal. Letting clients see project progress without a full account removes a class of status-update meetings. Most alternatives require a paid seat or don’t have this at all [website].
Meaningful v2.0. The Angular → React migration, redesigned Kanban, and dark mode in one release suggests active development momentum, not maintenance mode [3].
Clean UI. Multiple testimonials specifically mention ease of use and simplicity [website]. The Heise coverage describes the new Kanban as “more intuitive task management” [3].
Self-hosted with Docker. Standard deployment path, no exotic dependencies beyond MinIO [3].

Cons

AGPL-3.0, not MIT. If you embed Worklenz in a commercial product, AGPL requires you to open-source that product. For most self-hosters this doesn’t matter. For anyone building on top of it, it absolutely does [3].
Cloud free tier is genuinely limited. 5 members, 3 projects, 1 GB storage [1]. The “free forever” headline on the homepage is technically true for the cloud but practically useless for any real team.
No mobile app yet. Announced but not shipped as of the 2.0 release [3]. For field teams and agencies with mobile workers, this is a real gap.
S3 dependency. Object storage is required, not optional. Adds complexity for first-time deployers [3].
Small community. Under 3,000 GitHub stars, a modest Discord [website README]. Compare to Plane, Linear alternatives, or OpenProject — less community support means fewer tutorials, third-party integrations, and faster recovery when you hit a problem.
Missing: wikis, meeting management, forums. OpenProject’s comparison documents these gaps explicitly [1]. For teams that live in project wikis or need structured meeting notes tied to projects, this is missing.
Young codebase. The v2.0 frontend migration is a positive signal but also means the React frontend is relatively new. Expect rough edges.
Limited third-party reviews. The available reviews are thin. Most coverage is from OpenProject (competitive interest) or general tech news. No in-depth migration guides or long-term production reports found.

Who should use this / who shouldn’t

Use Worklenz if:

You run an agency or consultancy and you want project profitability and billable hours tracked in the same tool as your tasks.
You’re paying $100–$200/month on Asana or Monday.com for a 10-person team and want to cut that bill to near zero.
You have a technical person (or will hire one once) to handle Docker deployment and ongoing updates.
You want client-facing project visibility without buying client seats.
AGPL-3.0 doesn’t conflict with your business model.

Skip it (use Plane instead) if:

You want a similar open-source PM tool with a larger community, GitHub Issues-style interface, and MIT license.
You prioritize ecosystem integrations and third-party support over financial tracking.

Skip it (use OpenProject instead) if:

You need meeting management, project wikis, and forums alongside your task management.
You want a more mature self-hosted PM tool with a decade of production history and larger community.
GDPR data residency under German jurisdiction matters to your clients [1].

Skip it (stay on Asana or Monday.com) if:

You have no one to manage a server and no budget to pay someone to set it up.
Your team needs mobile apps today.
Your compliance requirements need a vendor with documented security certifications.

Skip it (use Linear) if:

You’re a software product team. Linear’s issue tracking, Git integration, and team workflows are in a different category — Worklenz is optimized for client services, not product sprints.

Alternatives worth considering

Plane — closer to Jira/Linear in positioning, MIT-licensed, 15,000+ stars, larger community. Missing the financial and agency-specific tooling that Worklenz targets.
OpenProject — most mature open-source PM tool, GPL v3, German company with GDPR focus. Has project wikis, meeting management, and forums that Worklenz lacks [1][2]. More complex to deploy.
Taiga — older open-source option with Agile focus. Less active development than it used to be.
Asana — the incumbent. Best-in-class UX and integrations, purpose-built mobile apps, but $10.99–$24.99/user/month scales badly and locks your data behind their API.
Monday.com — strong for visual project tracking, no self-hosting option, pricing comparable to Asana.
Trello — frequently mentioned in Worklenz testimonials as what teams are replacing [website]. Simple Kanban only, no time tracking, no financial views. If you’ve outgrown Trello’s simplicity, Worklenz is a reasonable next step.
Notion — frequently used as an all-in-one but lacks native time tracking and financial monitoring. Worklenz is more appropriate for teams that need the agency PM features Notion doesn’t have.

For an agency specifically evaluating SaaS escape, the realistic comparison is Worklenz vs OpenProject vs Plane: Worklenz wins on financial and billing tooling; OpenProject wins on maturity and documentation; Plane wins on community and developer experience.

Bottom line

Worklenz fills a genuine gap: it’s the only AGPL self-hosted project management tool built specifically for the financial realities of agency work. Profitability monitoring, billable hour capture, and client portals are built in rather than bolted on. For a 10-person agency paying $100+/month on Asana, self-hosting Worklenz on a $10 VPS is straightforward math.

The honest caveats: this is still a relatively young project, the React frontend is new as of 2.0, there’s no mobile app yet, the S3 dependency adds deployment complexity, and the community is thin compared to more established alternatives. The AGPL license is also a real consideration — it’s not the permissive MIT that n8n or Activepieces users are used to evaluating.

If you’re an agency founder who needs time tracking, budget monitoring, and client visibility on one screen, and you’re willing to spend a couple of hours on Docker setup, Worklenz is worth a serious look. If you want the most proven self-hosted PM tool in production, OpenProject is still the safer bet.