Building KinVeto — a safer way to protect families from remote access scams
by aaadisyHey everyone 👋
I’m building KinVeto, a cybersecurity product designed to help families stay safer from remote-access scams.
One thing that worries me is how easily scammers can convince someone to install a remote-access app and give them control of their computer.
The idea behind KinVeto is simple:
If someone tries to gain remote access, KinVeto can block it and give a trusted guardian the ability to decide whether that access should be allowed.
I’ve built and launched the first version, and now I’m focused on making it more useful, reliable, and easy enough for non-technical users.
I’m sharing the journey here because I’d love to learn from other indie hackers who have already built and launched products.
What would you prioritize first when building a security product for families — ease of use, stronger protection, guardian controls, or something else?
Would love to hear your thoughts. 🚀
Building in public with KinVeto.
-
1
The protection is meaningful only if people actually leave it enabled. Have early users encountered a real remote-access attempt and kept KinVeto in place, or is balancing protection against false blocks still the main unknown?
-
1
I’ve already validated the core protection myself — KinVeto stays active after reboot, works offline, runs quietly in the background, and blocks the remote-access tools I’ve tested. The next thing I’m validating with real users is the balance between strong blocking and avoiding false positives. The goal isn’t to make remote access impossible; it’s to make unauthorized access impossible while keeping legitimate access one-click and temporary.
-