# About Luuphub

A feedback platform built around one idea: the loop is not closed until the person
who asked hears back.

## What Luuphub is

Luuphub collects product feedback and carries it all the way to a reply. You
embed a widget on your site; your users send requests, bugs, and ideas without leaving
the page. AI triages what arrives — categorizing it and merging duplicates into one
thread instead of leaving you a list of near-identical tickets. From there each request
moves across a public board (Under review, Planned, Building, Shipped), and the
changelog announces the ship back to everyone who asked for it. That last step is the
whole point: most feedback tools are good at collecting and quietly bad at answering.

The same data is available to machines, not just people. There is a public REST API, an
MCP server for agents, outbound webhooks, and markdown mirrors of the docs — see the
[developer docs](https://luuphub.com/developers) for the full surface.

## Who makes it

Luuphub is built and run by Ainars Klavins. It is a small, independent product,
which shapes what it is good at: decisions get made quickly, the roadmap is not
committee-shaped, and the person answering <hi@aina.rs> is the person who writes the
code. The Terms of Service state that Luuphub operates under the law of the
Republic of Latvia.

## The pricing pledge

Luuphub will never be priced on your users. No tracked-user tiers, no MAU bands,
no page-view meters — because pricing on those turns your growth into our invoice and
quietly punishes you for putting the widget in front of more people. Plans are priced on
sites, admin seats, AI volume, and capabilities like API access and white-labelling.
That is not a marketing line: there is no tracked-user dimension anywhere in the plan
model to bill against. [Read the pledge on the pricing page](https://luuphub.com/pricing#pledge).

## EU hosting and your data

Application data and derived analytics are hosted in the EU, and error tracking and
product analytics are pinned to EU regions. Feedback is never used to train third-party
AI models — providers process it transiently to return a result. Export and erasure
tooling exists because GDPR obligations are yours as well as ours. [The data-processing
page](https://luuphub.com/data-processing) sets out the mechanics, and [the privacy
policy](https://luuphub.com/privacy) covers what we collect and why.

## What it is for

Luuphub suits teams who already get more feedback than they can read and want it
deduplicated, prioritized, and visibly answered: SaaS products, agencies running feedback
for client sites, and internal tools with real users. It is not an analytics product, a
support inbox, or a survey tool — it does one job, from asked to shipped. There is a free
tier with no card required if you would rather check than take our word for it.

Questions, or something that should be on this page and is not? Write to
[contact](https://luuphub.com/contact).