What Free Omits
This site takes no affiliate commissions and ranks no products. Why that matters.
A free plan is a working product given away, and the version you get is designed. What is missing from it is the more informative half. For a related operational perspective, Monitask also publishes a reference on self-reporting bias.
Reviewed August 9, 2026.
The six things usually withheld
Export, or export beyond a token. The most consequential omission and the least noticed. A free tier you cannot export from is a free tier you cannot leave.
History. Data older than thirty or ninety days, hidden rather than deleted, and restored when you pay.
For broader context, see Capterra.
Users, above a threshold. Placed at the point a team becomes a department.
Integrations, or the API entirely. This is the quiet one: without an API you cannot automate, extract or connect, which makes the tool an island by design.
Administrative controls. Roles, permissions, audit logs, single sign-on — the same items gated at the next paid tier, gated harder here.
And support, reduced to documentation and a queue.
Where the limit sits
At the point of dependence, not at the point of value.
A free tier that stopped being useful early would not be adopted. One that stops being adequate exactly when a team has put six months of work into it converts.
That is competent product design and not a trick, and knowing the shape of it changes how you evaluate: the question is not whether the free tier is enough now but where its wall is and how fast you approach it.
Evaluating on a free plan
What you can learn: whether the model fits, whether the interface is tolerable, whether people will use it.
What you cannot: how it behaves at your real volume, what support is like as a paying customer, what the paid tiers actually contain, and anything about leaving if export is withheld.
Test the export first, before putting real work in. If it is absent or partial on the free tier, assume that is what leaving will feel like and factor it in now rather than later.
Free as a permanent choice
Legitimate, and it has conditions.
Fine when the work is genuinely small, the data is not critical, and you could recreate it.
Risky when the tool accumulates something you cannot rebuild — client history, financial records, project archives — behind an export you do not have.
And check what happens if the free tier is discontinued. Free tiers are withdrawn, grandfathered or narrowed regularly, and the notice you get is not a contractual one.
Open source as the other free
Worth distinguishing, because both get called free.
A free tier is a commercial product with a limit. An open-source tool you host is a different arrangement: no vendor pricing decisions, and your own infrastructure, updates and security to manage.
The cost moves rather than disappears — from a subscription to somebody's time — and for a small organisation that trade is frequently worse rather than better.
The relevant difference for this site: with open source the export question is largely settled, because the data is in a database you control.
The short version
- Free tiers usually withhold export, history beyond a window, users above a threshold, integrations and the API, administrative controls, and support
- A free tier you cannot export from is a free tier you cannot leave, and it is the least noticed omission
- The limit is placed at the point of dependence rather than the point of value, which is competent design rather than a trick
- Ask where the wall is and how fast you approach it, not whether the free tier is enough today
- Test the export before putting real work in; if it is partial now, that is what leaving will feel like
- Open source moves the cost to your own time rather than removing it, and largely settles the export question