Demand for a locally runnable, privacy‑preserving browser automation agent
Problem
Users want to move Jev from cloud to local execution to avoid fees, reduce latency, and prevent telemetry leakage of credentials, while also addressing performance bottlenecks and runtime errors.
Pain points
- Desire to run locally on consumer hardware to avoid cloud fees and latency
- Concern about telemetry leaking credentials
- Concern about performance bottlenecks and runtime errors
Questions to verify
- Would you be willing to pay for such a locally runnable tool?
- What are your specific privacy concerns?
- What are the minimum hardware specifications required for local execution?
Evidence
quote · @Anonymous
I would be v excited if jev wasn’t a cloud model. Something that can run on consumer hardware at v fast speeds. Deffo impressive work. Don’t want to bring them down. I just don’t like paying AI tax to gate keepers for each use.
quote · @Anonymous
I had a look under the hood of browser-use. I wanted to to run some tests with a local browser and a trusted LLM provider of my choice, but the (enabled by default) telemetry they send to PostHog is CRAZY. Especially the browser-harness component can leak credentials to PostHog left and right. This is absolutely not cool.
quote · @Anonymous
The more I see about how Jev works, the less interested I get. Jev would be cool as a local model for e.g. Home Assistant. Projects like this are at best misleading, this one also happens to be broken.
quote · @Anonymous
Getting an error on the actual run demo button, no error on building.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.