Termerly is launching on Product Hunt on May 27, 2026. It's a free AI-powered platform that drafts privacy policies, terms of service, and cookie policies for any website. Paste a URL and the AI reads what the site actually does, then writes the legal pages from what it finds.

If you build software for a living and you have ever shipped a side project, you already know the moment we're about to describe. The product is ready, the domain is bought, the landing page looks decent. Then comes the reminder that the site still needs a privacy policy, terms of service, a cookie banner, maybe a DPA. You open a tab to Termly or Iubenda, fill in a wizard, and hit the wall. The free tier is a teaser. The paid tier feels overpriced for a single document. The moment a second project ships, the subscription stops making sense.

That wall exists for almost every indie builder. Termerly is the door.

The problem: legal pages are still a paywall for indie founders

The market for legal-page generators is dominated by a handful of vendors with similar pricing logic. Free tiers exist on paper, but they're engineered to be unusable for a real product:

  • One document per project on the free tier, even when a site needs three or four
  • Watermarked exports that say "Generated by [vendor]" on the customer-facing site
  • LGPD and PIPL clauses gated behind enterprise plans, despite those being the markets a small SaaS most needs to cover
  • Hosted pages locked to the vendor's domain, with no way to custom-domain them under the user's brand
  • No version history, no audit trail, no way to prove which version of a policy a user actually consented to

For a bootstrapped founder running a handful of products, the math gets ugly fast. Termly's per-domain pricing model turns a $20/month subscription into $80/month across four projects. Iubenda's per-site billing has the same problem. Neither was designed for the indie builder who ships three things a year. They were designed for the marketing team of a single SaaS company that signs once and stays for life.

The result is what you see across the indie SaaS scene today. Most small products either skip the legal pages entirely (legally risky), copy-paste a generic template from a free generator (legally inaccurate), or budget-bleed on a tool they don't fully need (operationally painful).

What Termerly does differently

The bet behind Termerly is that AI has changed the unit economics of drafting a legal page. Five years ago, generating a privacy policy that accurately reflects a specific website's data practices required either a lawyer or a complex rules engine. Today, an AI can read a live site, identify the SDKs installed, the payment processors integrated, the analytics scripts running, and the cookies set, and write a tailored policy in seconds.

That changes the pricing assumption. If the marginal cost of a generated document is close to zero, the free tier doesn't need to be a teaser. It can be the product.

The flow looks like this:

  1. Paste a URL.
  2. Termerly's AI inspects the site: SDKs, third-party scripts, payment integrations, cookies set on first load, analytics endpoints.
  3. It drafts the privacy policy, terms of service, cookie policy, and DPA, each accurate to what the site actually does, not a generic boilerplate.
  4. The documents are hosted on a permanent URL (with optional custom domain, free), version history with side-by-side diff, and a consent banner SDK that ties each user's acceptance to the specific policy version they saw.
  5. GDPR, CCPA, LGPD, and PIPL are covered in every policy by default, including the markets the legacy vendors gate behind enterprise.

And it's free forever. No card, no per-domain pricing, no upgrade prompts. The whole product is the free tier.

If compliance becomes accessible to indie founders and SMBs, more sites will actually be compliant. Today most small SaaS products either skip the legal pages or use templates that don't reflect what they actually do. Termerly fixes that without forcing them into a subscription they can't justify.

The tech stack

For the builders reading this, here's what's running under the hood. The full stack is also on StackShare for the granular view.

  • Marketing site: Astro 5 with Tailwind CSS 4. Fully static, sub-100KB initial load, Lighthouse 100 across the board.
  • Admin workspace (where policies are generated and edited): Nuxt 4 with Vue 3, PWA, Pinia, VeeValidate plus Zod, and a TipTap-based rich editor for inline policy edits.
  • Legal center (where hosted policies live for the public): another Nuxt 4 app, read-only, optimized for SEO and crawlability.
  • AI backend: FastAPI with Anthropic Claude as the drafting engine. Inter-service auth via shared key, fails closed in production.
  • Database: PostgreSQL on Neon with Drizzle ORM. Six tables, four views, every PK is a UUID with gen_random_uuid().
  • Auth: Firebase session cookies (httpOnly, secure, sameSite=lax), 7-day expiry, lazy-loaded SDK so the auth bundle never enters the boot path on cold pages.
  • Media: Cloudinary for image hosting and OG image generation via Satori at the edge.
  • Email: Resend with React Email templates.
  • Monorepo: Turborepo plus pnpm workspaces. Docker multi-stage builds, deployed on self-hosted Dokploy. CI on CircleCI.

If you're shipping a serious indie SaaS, that stack will look familiar. The pattern is straightforward. Pick boring, battle-tested infrastructure for the surfaces users touch, then invest the saved complexity budget in the one or two things that actually differentiate the product. For Termerly, that's the AI drafting and the consent SDK.

Why free forever

The honest answer is that the legacy pricing model is wrong, not that Termerly will never charge for anything.

Legal compliance is one of those line items every serious site needs but almost no one wants to think about. Charging a flat per-domain rate for a document that costs cents to generate is the kind of pricing that survives because nobody has had a reason to undercut it. AI-first generation gives someone a reason.

What's free in Termerly today is the full product: unlimited generators, hosted policies on a permanent URL, custom domain support, version history with diff, consent banner SDK with per-user audit trail, all four major jurisdictions (GDPR, CCPA, LGPD, PIPL). No card, no per-domain pricing, no upgrade prompts.

If a paid tier eventually shows up, it'll be for something the indie founder doesn't strictly need on day one. The core "draft, host, embed, version" loop stays free. That's the commitment.

The Product Hunt launch

Termerly launches on Product Hunt on Wednesday, May 27, 2026, at 09:01 CET (00:01 PT). The Coming Soon page is here for anyone who wants the launch-day notification.

Subscribe to the Product Hunt page above and you'll get a single notification when Termerly is live on launch day. No spam, no follow-ups, no email list capture. Just the one ping.

If you haven't tried Termerly yet, sign up and paste a URL. The whole feedback loop takes about 90 seconds. For comparison-shoppers, the Termerly vs Termly page lays out exactly where the two products diverge: pricing, jurisdictions, audit trail, custom domain. The same exercise applies to Iubenda, Cookiebot, OneTrust, Usercentrics, and Osano.

How to support the launch (if you want to)

Three concrete things that actually move the needle on launch day:

  • Notify on the Product Hunt page. Early notify-me's are factored into the launch ranking. One click.
  • Upvote on May 27 when the launch goes live. The first six hours after 00:01 PT decide the ranking.
  • Follow Termerly's Indie Hackers page, where the build-in-public updates land after launch.

If you happen to use Termly or Iubenda today and want to leave a comparison-shopper note on the AlternativeTo listing, that genuinely helps other indie founders find Termerly when they're looking to cut the bill.

If you're a founder, builder, or compliance person and you have feedback, a feature request, or a "this is missing", the fastest way to reach the team is through the app. Every message gets read.

See you on May 27.