The real cost of free

“It's free.”

Two very pleasant words.

You download the app, create an account and start using it.

Only later might you wonder who is paying for everything.

Servers, maintenance, staff, bandwidth and support all cost something.

Not paying directly doesn't mean the service has no cost.

The real question is: who pays, and what does that mean for users?

Not all free services are alike

One service is funded by advertising.

Another gives away basic features and charges for advanced ones.

A non-profit may rely on donations. A public service may use collective funding.

Open-source projects can be sustained by communities, foundations or businesses selling support.

These models are not identical.

“If you're not paying, you're the product” is a memorable warning.

But it doesn't accurately describe every free tool.

Advertising isn't automatically bad

A publication can offer articles for free because advertisers support it.

That's a familiar model.

The problem begins when it rewards misleading titles, artificially multiplied pages or unnecessary collection of personal information.

A site depending entirely on page views may feel pressure to prioritise volume over quality.

It doesn't have to happen.

But the incentive deserves attention.

Personal data carries responsibilities

An account can be genuinely useful: preferences, history, continuity across devices.

But every piece of stored data creates a responsibility.

Why collect it? Who can access it? How long is it kept? How can a person request deletion?

These questions matter for small apps too.

You don't need to build surveillance to deliver a good service.

And data collection isn't justified merely because it is technically easy.

The “free at first” trap

Another approach is to give most features away, attract users and change the rules later.

Some changes are reasonable. Services need sustainable funding.

But users can feel trapped when they've organised their work around a tool and its limits suddenly change.

That's why I care about export options and migration paths.

A good tool shouldn't become a prison.

What about my own products?

With KUMBA and other projects, monetisation is a real question for me too.

Advertising, subscriptions or other revenue models may be possible.

But I need to consider how those choices affect product quality.

If funding pushes me toward useless content, readers pay indirectly through wasted time and lost trust.

If basic features become confusing without a paid plan, early users may feel misled.

I don't have a perfect formula.

I'd rather ask the question early.

What I'd check before signing up

Before trusting a free service with my information or work, I'd ask:

• Who runs it?
• How is it funded?
• Which data is really needed?
• Can the terms change?
• Can I export my content?
• What happens when I need help?

Free products aren't automatically bad.

But informed choices are better.

The real cost of free isn't always money.

Sometimes it's time, attention, dependence or privacy.

What matters is understanding the exchange.