See. Control. Choose.
See observed app connections in today’s local Linux alpha. Our next steps: broader connection controls and optional, specifically approved paid research. Visibility comes first; participation stays your choice.
Local Linux alpha
Hopvio · Three tiers of agency
Start with understanding. Build toward more control and an informed choice about sharing. Each tier has its own stage of development.
Linux alpha today
Where does your data go?
Explore the connections between your apps and their destinations. Inspect the evidence, compare changes, and see where visibility ends.
Partial visibility—not every packet, its contents, or onward sharing.
Enforcement planned
Act when it matters.
Manage the records Hopvio keeps today. Next, we’re planning supported connection controls with clear scope, impact, and undo.
Blocking cannot recall sent data. Deleting local records does not erase a recipient’s copy.
Research phase
Share on your terms.
We’re exploring optional paid research and data licensing. Review a specific offer and choose whether to share a defined result with a willing buyer.
No marketplace is live. Earnings are not guaranteed, and existing trackers cannot be forced to pay.
A closer look
Explore apps and destinations in an understandable graph. Open a connection to see the observations behind it.
Capture a sample before an activity and another afterward. Compare which endpoints appeared, disappeared, or stayed.
Observations stay in memory by default. Choose encrypted local history, exclude apps, or delete retained observations.
How it works
Start with an app you want to understand and inspect its observed connections.
Read the evidence for each endpoint. Observed facts, inferred operators, and unknowns stay distinct.
Compare samples or annotate a connection as expected. You decide what deserves another look.
Where things stand
The Linux alpha uses socket polling to observe available app connections and can import supported sensor metadata. Optional Tetragon integration adds TCP event evidence on supported Linux setups; it does not provide complete traffic coverage. Coverage is partial: it cannot establish the exact content sent, every short connection, or what a server shares onward.
Pause Hopvio collection, exclude apps, choose local retention, or delete Hopvio’s records. These controls affect Hopvio’s observation history. Live connection blocking and guided external deletion requests are planned; current firewall plans are simulations. Hopvio does not produce malware verdicts.
No. Deleting Hopvio’s local record does not delete the recipient’s copy. Future blocking may stop supported transmissions, but cannot recall past deliveries. A request to an external service is a separate action whose completion depends on that service.
No. Tier 3 is an optional paid-research and data-licensing proposal, not a live marketplace. The planned flow requires you to approve a specific buyer, purpose, output, and reward before release. Declining or leaving would keep your visibility and protection features. Monitoring history would never be sold by default.
We are exploring studies funded upfront by willing research buyers, such as software teams seeking specific feedback or measurements. This demand still needs validation. Blocking a tracker cannot make it pay, and no offers or earnings are guaranteed. Hopvio’s visibility and controls remain useful without a marketplace.
They describe the product direction: See, Control, and Choose. They are not announced pricing plans. Partial visibility and local observation controls are available in the Linux alpha; live network enforcement and paid participation remain future work.
Subscribe below for Hopvio updates. It is an email subscription, not a product account or access grant. Broader platform support remains future work.
Follow Hopvio
Get occasional emails about Hopvio: progress, releases, and opportunities to give feedback.
Just Hopvio updates. Unsubscribe anytime.
Hopvio
Your Hopvio subscription has been saved. Thanks for following along.
Back to Hopvio