Local-first, no exceptions
The binary runs entirely on your machine. No product telemetry, no phone-home, no user database on our servers. Our infrastructure only receives payment and license-validation requests — nothing else.
What you can rely on, and what we will never promise. Vether's security rests on explicit architectural choices.
The binary runs entirely on your machine. No product telemetry, no phone-home, no user database on our servers. Our infrastructure only receives payment and license-validation requests — nothing else.
Vether is distributed only from vether.org. Any other source (mirror, torrent, forum) should be treated as untrusted and potentially modified.
The SHA-256 hash of every Windows x64 release is published at release time, on the download page and in the changelog. You can then verify the file's integrity with Get-FileHash in PowerShell before running it.
Periodic license validation is Ed25519-signed. An opaque license token travels, along with a random anti-replay nonce.
Our servers keep no product-usage logs. Technical access logs (infrastructure security: intrusion attempts, anomalies) expire automatically within 30 days and are never correlated with customer accounts.
Found a vulnerability? Write to us PGP-encrypted at [email protected]. First response within 72 h, coordinated fix. Acknowledgements program published in /security.txt at the site root.
Rather than reinventing cryptography, Vether orchestrates the open-source tools that have passed the test of time — and adds the interface, usage discipline and support they lack for a general audience.
Architecture: C# .NET 6+ · WPF · Autofac DI · WMI · P/Invoke Win32 · elevated PowerShell exec.
No home-grown cryptography. Every algorithm is standard, published and widely audited. Vether's job is to invoke them correctly, with the right parameters, at the right moment.