Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Testing a minimal WireGuard VPN infrastructure (DE + US nodes)

nokznokz Member

Hi everyone,

I’ve been experimenting with building a minimal privacy-focused infrastructure project called NOKZ.

The idea is to keep the architecture intentionally simple and predictable while reducing attack surface and avoiding unnecessary data collection.

The current layer is a WireGuard-based VPN with entry nodes running in Germany (Frankfurt) and the United States.

The long-term goal is to build a multi-layer privacy infrastructure where the VPN acts as the first layer and additional network-defense components build on top.

Current setup:

Protocol: WireGuard
Locations: Germany (Frankfurt), United States
Architecture: minimal infrastructure design
Focus: reduced attack surface and predictable networking

This is still early stage and I'm mainly interested in feedback from people here who run infrastructure or VPN nodes.

If anyone wants to test the service or look at the design philosophy, the site is:

https://nokz.io

Would appreciate any feedback or thoughts.

What matters most in a privacy-focused VPN infrastructure?
  1. Network architecture8 votes
    1. Transparency
      75.00%
    2. Network architecture
        0.00%
    3. Minimal Logging
        0.00%
    4. Server jurisdiction
      25.00%

Comments

  • OscarCiprianoOscarCipriano Member, Patron Provider

    i think this post violate the community rules

  • Interesting concept, but a few things stand out.

    Running on DigitalOcean, a US based company, means your traffic passes through infrastructure you don't control, subject to US jurisdiction and potential legal compulsion. That's a significant trust issue.

    Your Terms of Service mention account termination conditions that imply you can identify and act on user behavior. That's hard to reconcile with a no-logging claim. If you're truly not collecting data, how are you enforcing those terms?

    The website also looks AI generated, which doesn't inspire confidence, and there's no open source code to verify any of the claims being made. For a privacy-focused project, transparency isn't optional.

    It's the whole point.

    Thanked by 2buggedout r3k
  • aphexaphex Member

    "• privacy over marketing — no tracking, no noise" "no trackers" ... third party analytics included

    "transparency" ... no source code, "We intentionally keep technical details private" lol

    "infrastructure under our control" "controlled infrastructure" ... digitalocean vpses that can be ram dumped without warning

    no private crypto accepted, transparency have severe technical misunderstandings about what nokz "can" see vs what nokz "intentionally collects"

    Thanked by 1buggedout
  • risharderisharde Host Rep, Veteran

    I could be wrong but when I think about purchasing a VPN, my main want is privacy. That being said, laws are getting so advanced now that that's pretty much near impossible and therefore I don't really use VPNs from providers for privacy anyways - and since I'm not doing anything strange on the internet, I don't even bother with the VPNs - and that goes against most of what the opinions on LET would likely be. The thing is, we think we're sticking it to the big man when we use VPNs but we're just a drop in the bucket - they have more than enough user data to not care what we think.

  • tdy0923tdy0923 Member
    edited March 13

    I’m curious—can your NOKZ project bypass censorship? If so, I would consider recommending it on my project, https://Qilan.de

  • MannDudeMannDude Patron Provider, Veteran

    Would need to be on your own IPs / network for it to be mostly usable. Digital Ocean, Vultr, Hetzner, and other big player's IPs are all mostly already seen as high risk IPs for most websites. Just results in a lot of annoying CAPTCHAs and random security checks.

    For example, since I'm in South East Asia mostly nowadays so I needed a good Singapore based VPN. Used different VPS provider's from here, Vultr, etc to setup a private Wireguard server for my self. Was a real pain in the ass, non-stop security checks everywhere. Since we're opening a Singapore POP sometime soon anyway, I went ahead and announced a /24 in Singapore (which is mainly just used at the moment for DNS / VPN development stuff) and those issues all went away. Currently just using Vultr for BGP, but since I'm using a clean IP space I'm not getting all the headache and hassle online that I was before.

    With that said, any VPN provider that isn't being managed or owned by some Israeli tech firm is welcomed.

  • zedzed Member

    Everything about this screams a-v-o-i-d, not sure what you were thinking.

    Thanked by 1buggedout
Sign In or Register to comment.