Zulivio Is Actually Free — Here's What AGPL-3.0 and Self-Hosted Really Mean
“Free” is the most abused word in software marketing — free trial, free tier, free up to five seats, then a bill. So it’s a fair question when a CRM and workforce-operations platform says it’s free: free how, and for how long? With Zulivio the answer is boring in the best way: it’s AGPL-3.0-licensed open-source software. There is no trial period, no seat cap, no feature paywall, and no point at which a bill arrives.
What AGPL-3.0 actually grants you
The GNU Affero General Public License v3.0gives you, in plain terms: the right to run Zulivio for any purpose, including commercially; the right to read, modify, and audit every line of the source; and the right to redistribute it, modified or not. None of that is time-limited or seat-limited, because none of it is a pricing tier — it’s the license the software ships under, full stop.
The one obligation AGPL adds beyond a permissive license like MIT: if you take a modified version of Zulivio and run it as a network service for other people, you have to make that modified source available to those users under the same license. This is the “network copyleft” clause AGPL is known for, and it exists to close the loophole where a company could fork an open-source project, host it as a paid service, and never contribute anything back. If you’re running Zulivio internally for your own team — the normal case — this clause simply doesn’t come up.
What “free” doesn’t mean
Open source and free-of-charge aren’t the same claim as “costs nothing at all,” and it would be dishonest to pretend otherwise. Zulivio still needs a machine to run on — your own hardware, a home server, or a low-cost VPS — and that machine has a cost, the same way a filing cabinet or a till has a cost. What disappears is the recurring, scaling cost: no per-seat fee that grows every time you hire, no feature you have to upgrade a tier to unlock, and no vendor deciding next quarter’s price increase for you.
There’s also no dedicated support hotline bundled in — you get the source repository and an issue tracker, not a phone number. For a small team comfortable running a Docker container, that trade is straightforward. For a team that wants a managed, supported deployment, that’s a real difference from a paid SaaS product, and worth weighing honestly rather than glossing over.
Where the real cost goes instead
Run the arithmetic on a typical per-seat workforce tool: a modest per-employee monthly fee, multiplied by headcount, multiplied by twelve months, compounding every year as the team grows. That number doesn’t buy more software — the software is the same for every customer — it buys hosting, support, and margin on top. Self-hosting Zulivio moves that spend to infrastructure you already have or a VPS costing a few dollars a month, largely flat regardless of headcount. The install itself is a single command:
git clone https://github.com/Raktim94/zulivio.git && cd zulivio && ./install.sh
That script checks for Docker, generates a secure database password, builds the images, and starts the stack — no license key to request, no account to create before you can even evaluate it.
Why this is also a data question, not just a pricing one
Free-of-charge is one half of the argument; where the data lives is the other, and the two are connected more than they first appear. A per-seat SaaS product’s pricing exists partly to cover storing and processing your data on its infrastructure — data you then don’t fully control. Self-hosting removes that coupling entirely: your employee records, attendance history, and assignment data live in a PostgreSQL database in a Docker volume on your own server, not on someone else’s cloud. The full reasoning is in why self-hosting your team’s data matters.
Read the installation guide or see the three-step quick start on the homepage.