loupfeed is a single platform for the signals that come out of a live product — what users say, what they did, what broke, and how it all demos. Every one of them anchored to the element it happened on and the line of code behind it, on the web and inside your mobile app.
React, Vue, Svelte, React Native and Expo · npm i @loupfeed/react · source-available, self-hostable.
Install loupfeed once and turn on what you need. They share the same capture layer, the same backend, the same dashboard — so a crash, a replay and a piece of feedback all point at the same place in your code.
Users point at the exact thing that is wrong, and you get the exact line of code behind it.
Write a walkthrough once and let it play like a person would — every release, without re-recording.
The minute before it went wrong, kept in a rolling buffer and uploaded only when something happens.
Errors captured on their own, grouped, and resolved back to source with the session that led there.
Most tools in this space stop at the browser, then hand you a mobile SDK that can do a fraction of the job. loupfeed treats React Native and Expo as a first-class surface: the same four products, the same dashboard, the same resolution back to source — built for a world with no DOM.
Long-press anywhere in the running app and loupfeed hit-tests the actual native view under the finger, then pins feedback to it.
Two engines: real screenshots at a few frames a second, or a pure-JS wireframe with no native dependency at all.
The Metro tagger threads an identity through your components, so a pin on a mobile screen lands on a line in your repo.
loupfeed does not bundle a chatbot, and it does not quietly forward your users' data to a model somebody else picked. Everything all four products capture is exposed as MCP tools, so the agent you already trust reads it, fixes it, and closes the loop — with your keys, on your infrastructure.
Bring Claude, or whatever you run in-house. No vendor model sits in the path, and there is nothing to opt out of.
A replay arrives as an action timeline — scrolled, clicked, typed — instead of a video your agent cannot watch.
The same tools reply to the reporter and set the status, so “fixed” reaches the person who reported it.
Under all four products sits the same engine: a framework-agnostic core, thin adapters for the framework you use, and a build step that maps what your users touch back to where it lives in your repo.
React, Vue, Svelte on the web. React Native and Expo on mobile. Bundler plugins for Vite, Webpack, Rollup, esbuild, Babel and Metro.
Replays are masked by default and your source paths never reach the client bundle — that one is enforced in CI, not promised in a policy.
On your laptop, in one Docker container on a small VPS, or as CDK stacks in your own AWS account. Same API, same dashboard.
One command while you develop. Nothing to sign up for.
A small VPS or an EC2 box. API and dashboard together, durable on a volume.
Three stacks into your own account, configured entirely by environment.
A deployment is a single named instance bound to one product, so there is no project setup to do in the UI. Set the name at deploy time, open the dashboard, copy the DSN into your app.
Free to self-host, forever, and source-available so you can read every line before you trust it with your users. If you would rather not run it yourself, I will run it for you.