Softwr

Cybersecurity · head to head

Termly vs Umami

Termly logo

Termly

Cybersecurity

Legal policy generator and cookie consent banner for small websites

From
Free
Rated
-
Umami logo

Umami

Marketing

Open source, cookie-free web analytics you can self-host for the cost of a database

From
Free
Rated
-

The short version

  • Each has a real cost: Termly a standard plan licenses one website, so an agency or a business with several brand domains multiplies the headline price by the number of sites and the cheap option stops being cheap at four or five domains.; Umami there is no cohort analysis, retention curve, session replay or multi-touch attribution, so a marketing team that needs to justify channel spend will still buy a second tool and Umami becomes a supplementary dashboard.
  • They diverge on capability: Termly covers Policy generator, Umami covers Cookie-free tracking.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Termly and Umami actually diverge.

Attributes where Termly and Umami differ
AttributeTermlyUmami
Pricing modelPer website per monthPer month by event count
PlatformsWebWeb, Linux
CategoryCybersecurityMarketing

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Termly

  • Policy generator
  • Automatic policy updates
  • Consent banner
  • Script auto blocker
  • Cookie scanner
  • Consent log
  • WordPress plugin
  • Do not sell handling

Only in Umami

  • Cookie-free tracking
  • Self-hosting
  • Small tracking script
  • Custom events
  • Funnels and goals
  • Multi-site and teams
  • Public dashboards
  • API access

What people use each for

The jobs each tool is most often brought in to do.

Termly

  • A small e-commerce shop that needs a privacy policy, terms and a compliant cookie banner before launch without engaging a solicitornot Umami
  • A freelance web developer standardising the legal and consent layer across client sites, buying a licence per site or an agency arrangementnot Umami
  • A WordPress site owner who needs scripts blocked before consent and does not have a tag manager set upnot Umami
  • A US small business newly in scope for a state privacy law that needs a do not sell opt-out on the site quicklynot Umami

Umami

  • A developer who wants traffic numbers on a personal or client site without adding a consent bannernot Termly
  • An organisation whose legal or procurement team has ruled out sending visitor data to a US advertising companynot Termly
  • A high-traffic site where hosted analytics priced by pageview band has become expensive and self-hosting removes the ceiling entirelynot Termly
  • A team that wants analytics data in a database they already control so they can query and join it themselvesnot Termly

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Termly

  • A standard plan licenses one website, so an agency or a business with several brand domains multiplies the headline price by the number of sites and the cheap option stops being cheap at four or five domains.
  • Generated policies are templates conditioned on questionnaire answers, so they describe the data practices you claimed rather than the ones your code performs, and a regulator comparing the policy to actual tracking finds the gap not the vendor.
  • Banner view limits apply on the lower tiers, and a site that spikes in traffic can exhaust its allowance mid month, which is the worst possible moment for consent handling to degrade.
  • It covers websites well but has little for mobile apps, so a company with an iOS and Android app alongside its site needs a second consent mechanism and a second consent record.
  • There is no data mapping, subject rights automation or vendor inventory, so any company that grows into real privacy programme obligations outgrows Termly entirely rather than upgrading within it.

Umami

  • There is no cohort analysis, retention curve, session replay or multi-touch attribution, so a marketing team that needs to justify channel spend will still buy a second tool and Umami becomes a supplementary dashboard.
  • Self-hosting is only free in licence terms; you own the database, the upgrades, the backups and the query performance at scale, and a busy site's events table grows quickly enough to need real attention.
  • Because it stores no persistent identifier, it cannot follow a user across devices or sessions in any meaningful way, which makes returning-visitor and lifetime-value questions unanswerable by design rather than by omission.
  • Cloud overage is billed per event beyond the plan allowance, so a traffic spike or a badly instrumented custom event can produce a bill materially above the $20 or $200 headline before anyone notices.
  • It is maintained by a small team, so the pace of new capability is modest and enterprise expectations such as SSO, granular role permissions and formal support agreements are limited compared with commercial analytics vendors.

Pricing, plan by plan

Termly

Free
  • FreeFree
    • 1 basic legal policy
    • 10,000 monthly banner views
    • Cookie consent banner
  • Starter$10/month
    • 2 legal policies
    • 10 policy edits
    • 50,000 monthly banner views
  • Pro Plus$15/month
    • Unlimited banner views
    • Additional legal policies
    • Multilingual banners

Umami

Free
  • Self-hostedFree
    • MIT licensed, no licence fee
    • No event limit imposed by the software
    • Unlimited websites and users
  • Cloud HobbyFree
    • Up to 100,000 events per month
    • 3 websites
    • 6 months data retention
  • Cloud Pro$20/month
    • Up to 1,000,000 events per month
    • Unlimited websites
    • Unlimited team members
  • Cloud Business$200/month
    • Up to 10,000,000 events per month
    • All Pro features
    • Higher volume overage rate

Which should you pick?

Choose Termly if

  • You need policy generator.
  • You want to start without paying.
  • You also want automatic policy updates.

Choose Umami if

  • You need cookie-free tracking.
  • You want to start without paying.
  • You work on Web, Linux.
  • You also want self-hosting.

Questions people ask

Is Termly or Umami better?
Neither clearly leads. Termly starts at Free and Umami at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Termly or Umami?
Termly starts at Free and Umami at Free.
Does Termly or Umami run on more platforms?
Termly runs on Web. Umami runs on Web, Linux.
Can I use Termly for free?
Both have a free tier, so you can try either at no cost before committing.
What is Termly best used for?
Termly is most often used for a small e-commerce shop that needs a privacy policy, terms and a compliant cookie banner before launch without engaging a solicitor, a freelance web developer standardising the legal and consent layer across client sites, buying a licence per site or an agency arrangement, a wordpress site owner who needs scripts blocked before consent and does not have a tag manager set up, a us small business newly in scope for a state privacy law that needs a do not sell opt-out on the site quickly. Of those, a small e-commerce shop that needs a privacy policy, terms and a compliant cookie banner before launch without engaging a solicitor and a freelance web developer standardising the legal and consent layer across client sites, buying a licence per site or an agency arrangement are not what Umami is typically brought in for.
What can Termly do that Umami cannot?
Termly covers Policy generator, Automatic policy updates, Consent banner, Script auto blocker. Umami covers Cookie-free tracking, Self-hosting, Small tracking script, Custom events.

Answered from the vendors’ own pages

Termly: Does one Termly plan cover all my websites?

No. A standard plan licenses one website. Multiple domains need multiple licences or an agency arrangement, and this is the single most common surprise on the bill.

Umami: Is Umami really free?

Self-hosted, yes; it is MIT licensed with no event cap. You pay for the server and database. Umami Cloud has a free tier at 100,000 events a month and paid tiers from $20.

Termly: Are the generated policies legally sufficient?

They are templates conditioned on your answers and are not legal advice. They are proportionate for a simple site and inadequate where actual data flows are complex or regulated.

Umami: Do I need a cookie consent banner?

For Umami analytics specifically, generally no, because it sets no cookies and stores no personal data. Other tags on your site may still require one.

Termly: Is there a genuinely free plan?

Yes, one basic policy, one site, 10,000 monthly banner views and quarterly cookie scans, with no card required.

Umami: Can it replace Google Analytics?

For traffic, referrers and event counts, yes. For attribution modelling, audiences and advertising integration, no.

Termly: Does it handle US state privacy opt-outs?

Yes, including a do not sell or share mechanism and regional rule sets, alongside GDPR consent for EU visitors.

Umami: What does it need to run?

A container and a PostgreSQL or MySQL database. Most people deploy it on infrastructure they already pay for.

Share

Related pages

Other head to heads