ITFlow

Client IT documentation, ticketing, invoicing and accounting for MSPs (Managed Service Providers).

Healthy · 78
78/100
Healthy

Actively maintained with regular releases.

Maintenance 31/40
Releases 25/25
Community 7/20
Momentum 15/15

Commit activity more than 77% of tracked projects; popularity more than 36%. How this is calculated.

Commits, last 11 months

2025-12: 40 commits 2026-01: 80 commits 2026-02: 70 commits 2026-03: 135 commits 2026-04: 42 commits 2026-05: 17 commits 2026-06: 27 commits 2026-07: 215 commits 2026-08: 202 commits 2026-09: 66 commits 2026-10: 178 commits
2025-12 1072 total 2026-10
Stars1.1k
Latest releasev26.11 · 29 Oct 2026
Repo updated13 Nov 2026
LicenceGPL-3.0
Built withPHP

Is ITFlow actively maintained?

Over the last 11 months the project absorbed 1072 commits, of which 446 arrived in the most recent quarter — roughly 149 commits a month.

Activity is accelerating: the last quarter carried 72% more commits than the one before it.

The most recent tagged release, v26.11, shipped within the last month — a current, installable version exists today.

Of the 23 projects we track in Ticketing, ITFlow ranks #5 by health score — in the top quarter of its category.

What ITFlow actually does

ITFlow is a self-hosted platform designed for Managed Service Providers to handle client IT documentation, support ticketing, invoicing, and accounting tasks. Built with PHP under the GPL-3.0 licence, it provides a centralised system to track client assets and service requests. It serves as an open-source alternative to proprietary PSA and documentation tools.

Best fit: Managed Service Providers and independent system administrators who want to host their own client management and ticketing stack without paying per-seat SaaS fees.

Worth knowing: Adopting an open-source MSP platform means you are entirely responsible for data security, backups, and recovering from integration or billing errors. It also carries the usual migration overhead of moving existing client data away from established commercial alternatives.

Deployment notes

As a PHP application, it typically requires a standard web server stack such as Apache or Nginx alongside a relational database like MySQL or MariaDB. You will also need to configure persistent storage for uploaded documents and a reverse proxy to handle TLS termination.


ITFlow as a replacement for


Alternatives to ITFlow

Projects in the same categories, ordered by health score.