IT documentation, ticketing, and billing for small MSPs — honestly reviewed. No marketing copy, just what self-hosting a GPL-licensed PSA actually looks like.

TL;DR

What it is: Free, open-source Professional Services Automation (PSA) platform built specifically for small MSPs — client documentation, ticketing, billing, accounting, and a client portal in one PHP application [README][5].
Who it’s for: Small managed service providers (1–15 techs) who are either too small to justify ConnectWise’s pricing, or who want to stop paying per-seat fees entirely and own their own ops data [2][README].
Cost savings: The commercial PSA market starts at $35–$79/seat/month (HaloPSA, SuperOps) and runs to $130+/tech/month for Syncro. ITFlow self-hosted costs $0 in licensing plus $5–15/month for a VPS [2].
Key strength: Genuinely covers the full MSP PSA surface — documentation, tickets, invoices, accounting, passwords, client portal — without fragmenting you across five separate SaaS tools. It’s the only free GPL option that even attempts this scope [README].
Key weakness: Small two-person part-time team, PRs from the community are temporarily paused, no managed hosting yet, and the LAMP stack (Apache + MariaDB + PHP) isn’t the easiest to maintain compared to modern Docker-first tools [README][3].

What is ITFlow

ITFlow is a self-hosted PSA platform built by MSPs, for MSPs. The origin story is straightforward: in 2018, the founding team was running a small managed service provider and couldn’t find open-source tooling that covered everything a real MSP needs without costing $40 per technician per month. So they built it. By March 2019 it was on GitHub. By January 2025, seven years later, it finally hit a stable release [homepage].

The GitHub description calls it “All in One PSA for MSPs, which Unifies client, contact, vendor, asset, license, domain, SSL certificate, password, documentation, file, network and location management with ticketing and billing capabilities, with a client portal on the side” [README]. That’s a genuinely long list, and unlike many open-source tools that bolt on half-finished modules, ITFlow was designed from the start around the actual workflow of an MSP: document client environments, handle support tickets, invoice clients, reconcile the accounting, let clients check their own ticket and invoice status.

The README positions it directly as “a completely free & open-source alternative to ITGlue and Hudu” — two documentation tools that many small MSPs pay separately for on top of their PSA. That double-spend is exactly what ITFlow eliminates [README].

The project is licensed under GPL-3.0. Not MIT. That matters if you want to embed or resell it — GPL requires derivative works to also be GPL. For internal MSP use, though, it’s irrelevant: GPL means free to use, modify, and self-host without restriction [README].

As of this review, the project sits at 913 GitHub stars. It’s a small number compared to tools like n8n or Nextcloud, but PSA software is an extremely narrow vertical — 913 stars in the MSP community represents real adoption, not just curiosity.

Why people choose it

The reviews and forum threads converge on a single theme: cost vs. scope. Small MSPs get squeezed from both sides. ConnectWise and Autotask charge enterprise prices and require enterprise-level setup effort — one Capterra reviewer called using ConnectWise “very confusing if you don’t train on it for at least a few weeks” and another described the decision to migrate as “regrettable” [2]. Syncro and SuperOps are more approachable but run $79–$179 per technician per month [2]. For a three-person MSP shop, that’s $240–$540/month just for the operations platform before you buy anything else.

The flamingo.run MSP PSA comparison [2] lays out the commercial landscape with no affiliate links and no softening: ConnectWise doesn’t publish pricing, Autotask requires annual contracts, and the switching cost between PSA platforms is “3–6 months to fully migrate billing, ticketing, and workflows.” Vendors know this, and price accordingly.

ITFlow’s answer is: GPL license, self-hosted, $0 in licensing. The trade-off is obvious — you’re not getting ConnectWise’s distributor procurement integration or HaloPSA’s AI-driven ticket routing. You’re getting a solid, full-coverage PSA that a small shop can actually afford to run.

The SourceForge listing [1] puts ITFlow alongside commercial alternatives like Atera, which markets “AI agents” and “autonomous IT management” to 13,000+ customers. ITFlow doesn’t have marketing claims like that. It has a live demo at https://demo.itflow.org with credentials [email protected] / demo. That transparency is a signal: the team is confident enough in the product to let anyone poke around without a sales call.

Features

Based on the README, homepage, and documentation:

Client documentation hub:

Contacts, locations, vendors, assets (hardware inventory), software licenses, domains, SSL certificates, passwords, documents, files, and network diagrams — all linked to a single client record [README]
AES-encrypted password manager built in — no need for a separate tool like Bitwarden Teams for client credentials [homepage]
Domain and SSL certificate expiry alerting [README]

Ticketing:

Create, prioritize, and track support tickets [homepage]
Inbound email-to-ticket parsing: forward support@ emails into ITFlow and they automatically create or update tickets [docs][3]
Calendar integration for scheduling technician visits and client events [homepage]

Billing and accounting:

Quotes, invoices, recurring invoices, automated payment reminders [homepage]
Stripe integration for client online payments [homepage]
Full accounting module — income, expenses, payroll, assets, reports [homepage]
Lead management for the pre-sale pipeline [homepage]

Client portal:

Self-service access for clients: ticket status, invoices, important documents [homepage]
Reduces ticket-status emails from clients who just want to know where their support request stands [homepage]

AI integration:

Supports Ollama and LocalAI for private, self-hosted AI inference [homepage]
External integrations with ChatGPT [homepage]
AI assistance across ticketing, billing, documentation, and text editing [homepage]
Note: this is AI-as-assistant, not autonomous agents — it helps write tickets and docs, not replace the technician

API:

REST API for integration with RMMs and CRMs [homepage]
The docs describe it as “powerful” but the depth isn’t independently benchmarked here — treat that claim skeptically until you test it against your specific RMM

Modularity:

Individual modules can be disabled — if you only want documentation, you can turn off billing and ticketing [homepage]
Useful for shops that already have a billing tool and want ITFlow only for its documentation strengths

Pricing: SaaS vs self-hosted math

ITFlow:

Software license: $0 (GPL-3.0) [README]
Managed hosting: listed as “coming soon” on the homepage — not yet available as of this review [homepage]
Self-hosted VPS: $5–15/month on Hetzner, Contabo, or equivalent

Commercial PSA market for comparison [2]:

ConnectWise PSA: ~$25–35/tech/month estimated (no public pricing); enterprise deals average ~$9,000/year per Vendr data
HaloPSA: $35–109/agent/month
Syncro: $129–179/tech/month (includes bundled RMM)
SuperOps: from $79/seat/month
Autotask: contact vendor, annual contract required

Concrete math for a 3-tech MSP:

Tool	Monthly cost	Annual cost
ConnectWise (est. $30/tech)	~$90/mo	~$1,080/yr
HaloPSA (mid-tier, $65/tech)	~$195/mo	~$2,340/yr
Syncro ($150/tech)	~$450/mo	~$5,400/yr
SuperOps ($79/seat)	~$237/mo	~$2,844/yr
ITFlow self-hosted	~$10/mo (VPS)	~$120/yr

The savings range is $960–$5,280 per year for a 3-tech shop. That’s real money for a small MSP running on thin margins.

The honest caveat: ITFlow doesn’t include an RMM, and Syncro does. If you’re pricing Syncro, factor in that you might need a separate RMM for ITFlow — Tactical RMM, MeshCentral, or Wazuh, depending on your needs. The apples-to-apples comparison is ITFlow + a free/cheap RMM versus Syncro, which changes the math somewhat but still favors ITFlow significantly [2].

Deployment reality check

ITFlow runs on a LAMP stack: Linux, Apache, MariaDB, PHP. The recommended install method is a bash script on Debian/Ubuntu — one wget and one bash command and the script handles Apache, MariaDB, PHP, Let’s Encrypt certs, and cron setup [README][3]. There’s a video walkthrough linked from the docs for people who want to follow along visually [README].

If you prefer not to use the script, the manual APT path is well-documented: install Apache, MariaDB, PHP with the right extensions, clone the repo into /var/www/html, configure Apache SSL, set up the database, run through the web installer [4]. It’s not a single-command Docker pull, but it’s not arcane either.

Docker support exists but is labeled “community supported” — meaning the core team doesn’t maintain it and support is limited if something breaks [3]. The mariushosting.com guide [5] shows a working Docker Compose setup for Synology NAS, which is useful for home lab or lightweight deployments, but the entrypoint.sh file referenced in that guide requires a donation to download, which is worth noting if that’s your deployment path.

What you actually need:

A Debian/Ubuntu Linux server (VPS or bare metal)
A domain name (Let’s Encrypt requires it)
An SMTP relay for outbound email (invoicing, ticket notifications) [3]
About 1–2GB RAM for light use; more as client count grows

What can go sideways:

The README includes an explicit security caveat: “no system is risk-free. Nearly all software has bugs. Use your best judgement before storing highly confidential information in ITFlow.” That’s honest, but it’s also a genuine flag if you’re planning to store client passwords and sensitive network diagrams from day one [README].
The project’s self-update mechanism (git pull) means your web server user needs write permissions to the web directory. The manual docs handle this with chmod -R 775, which is functional but not maximally hardened [4]. Plan to run it behind a reverse proxy with proper firewall rules.
Inbound email-to-ticket setup is listed as “post-installation essential housekeeping” but isn’t configured by the install script — you handle it separately [3].
The master encryption key (used for the password manager) is critical to back up. Lose it, lose your stored passwords. The docs flag this but don’t automate the backup [3].

Realistic time estimates: For a technical user comfortable with Linux, 45–90 minutes from a fresh Debian VPS to a working ITFlow instance. For someone following the video guide with no prior Linux experience, a full afternoon, including DNS propagation and SMTP troubleshooting.

Pros and Cons

Pros

Actually free. GPL-3.0, no per-seat fees, no per-technician pricing, no vendor lock-in. For a 3-tech MSP, that’s thousands of dollars a year versus the commercial alternatives [2].
Full PSA scope in one install. Documentation + tickets + billing + accounting + client portal + passwords. Most free alternatives cover one or two of these; ITFlow covers all of them [README][homepage].
Built by MSPs who actually use it. The problem statement in the README reads like someone who lived it: scattered client docs, spending more time finding documentation than fixing problems, inconsistent invoicing. That specificity shows in the feature choices [README].
Self-hosted AI options. Ollama and LocalAI support means client data for AI-assisted ticketing and documentation never leaves your infrastructure [homepage].
Live demo. Anyone can log in at https://demo.itflow.org before committing to an install. That’s the right level of confidence in a product [README].
Stable release as of January 2025 — the project ran in pre-stable for six years before calling itself production-ready. Cautious, not cowboy [homepage].
Modular. Turn off what you don’t use. If you already have billing sorted, use ITFlow for documentation only [homepage].

Cons

Two-person part-time team. Johnny and Marcus are MSP practitioners first, ITFlow developers second. The homepage says it plainly: “Although ITFlow isn’t our primary job.” That’s admirable honesty, but it means responsiveness to bugs and new features is constrained [homepage].
Community PRs are paused. The README states: “We have temporarily paused PRs from the community.” No explanation given, no timeline for resumption. For an open-source project, closing external contributions is a yellow flag [README].
LAMP stack, not Docker-native. The recommended path is a traditional Linux server with Apache and MariaDB, not a docker compose up. Docker is community-supported with limited official backing [3]. If your ops team lives in containers, you’re somewhat on your own.
No managed hosting yet. The “Hosting (Coming Soon)” section has been on the homepage for a while. Until it ships, non-technical MSP owners who don’t want to touch a Linux command line have no easy path to ITFlow [homepage].
913 stars is a small ecosystem. The community is active (there’s a forum and bug tracker) but third-party plugins, integrations, and community guides are thin compared to larger tools. You’re more likely to hit an edge case with no documented solution [README].
GPL-3.0, not MIT. If you want to embed ITFlow in a product you sell, or fork it into a white-labeled MSP platform, GPL-3.0 requires your derivative work to also be GPL. Most small MSPs won’t hit this constraint, but it’s worth knowing [README].
Security caveat is explicit. The project itself tells you not to store highly sensitive information without applying your own judgment. For an MSP that stores client network passwords and infrastructure docs, that’s a meaningful risk disclosure [README].

Who should use this / who shouldn’t

Use ITFlow if:

You’re running a 1–10 tech MSP and you’re paying $200–$500/month for PSA software that you use maybe 30% of.
You’re currently using three separate tools (a documentation app, a ticketing tool, and a billing system) and the integrations between them are fragile or nonexistent.
You have basic Linux server skills or someone on your team does, and you’re willing to own the infrastructure.
You want to store client data — passwords, network diagrams, asset inventories — in a system you fully control, not a SaaS vendor’s cloud.
You can live with a small, part-time development team in exchange for a $0 licensing bill.

Skip it if:

You need a fully managed, supported SaaS with an SLA and a support phone number. ITFlow has a community forum, not a customer success team.
Your MSP is 20+ techs and you need enterprise features: fine-grained RBAC, advanced SLA management, procurement integration with Ingram or Synnex. ConnectWise is the tool for that, like it or not [2].
You’re non-technical and have no one to deploy and maintain a Linux server. Until managed hosting ships, there’s no easy button.
You need a built-in RMM. ITFlow handles PSA; remote monitoring requires a separate tool like Tactical RMM or MeshCentral.
You need active community-contributed extensions and integrations. PRs are currently paused and the third-party ecosystem is thin [README].

Alternatives worth considering

ITGlue — the documentation tool ITFlow explicitly replaces. Cloud-only, strong integrations with ConnectWise and other commercial PSAs, expensive ($29+/user/month). If you’re paying for ITGlue, ITFlow’s documentation module covers roughly the same ground for $0 [README].

Hudu — another ITGlue alternative, slightly cheaper, also documentation-focused. Self-hostable, actively developed, stronger UI than ITFlow’s documentation side. If documentation is your primary need and you don’t want ITFlow’s billing complexity, Hudu is worth evaluating.

HaloPSA — the commercial PSA with the best reputation for small-to-mid MSPs right now [2]. $35–109/agent/month, strong ticketing and billing, good UI, no open-source version. If you want a fully supported commercial option and can justify $100–200/month for a small team, HaloPSA is the realistic choice.

Syncro — bundled PSA + RMM, which ITFlow can’t match without a separate tool. $129–179/tech/month [2]. If you’re deciding between Syncro and ITFlow + Tactical RMM, the total cost is closer than it looks, but Syncro is a single-vendor relationship.

GLPI — older, open-source ITSM and asset management platform. More IT department–focused than MSP-focused, heavier to configure, but GPL and free. If you need ITIL compliance features ITFlow doesn’t cover, GLPI is the alternative.

Snipe-IT — if you only need asset management, Snipe-IT is MIT-licensed, actively maintained, and much simpler to deploy. Don’t use ITFlow just for assets when Snipe-IT is the right tool.

For small MSPs choosing between free and paid: the realistic shortlist is ITFlow vs HaloPSA. ITFlow if you can deploy and maintain a LAMP server and need to eliminate licensing costs. HaloPSA if you need a supported product and can budget $100–200/month.

Bottom line

ITFlow is the only serious free option for MSPs who need a PSA that actually covers documentation, ticketing, billing, and accounting without paying per seat. The trade-off is real: you’re running a GPL PHP app maintained by two people in their spare time, community contributions are currently paused, and managed hosting doesn’t exist yet. For a small MSP tired of watching $300–500/month disappear to PSA licensing fees, those trade-offs are very manageable. For a 20-person MSP shop that needs enterprise governance, advanced SLA management, and a support contract, they’re not.

The “coming soon” managed hosting option, if it ships, would make ITFlow accessible to non-technical MSP owners who want the cost savings without touching a Linux server. Until then, it’s squarely a tool for the technically capable or those willing to hire someone to stand it up once — which is exactly the kind of one-time deployment that a studio like upready.dev does for clients.

Sources

SourceForge — ITFlow Reviews (product page, 2026). https://sourceforge.net/software/product/ITFlow/
Kristina Shkriabina, Flamingo — “Best MSP PSA Software: Reviews and Comparison (2026)” (March 16, 2026). https://www.flamingo.run/blog/msp-psa-software
ITFlow Docs — “Installation” (updated November 18, 2025). https://docs.itflow.org/installation
ITFlow Docs — “Installation via apt”. https://docs.itflow.org/installation_apt
Marius Hosting — “How to Install ITFlow on Your Synology NAS” (guide for v26.3). https://mariushosting.com/how-to-install-itflow-on-your-synology-nas/