Dropped an update I’ve been wanting since day 1. Crypto payments are now 100% sovereign. We no longer depend on a third party. We operate our own nodes for 6 chains :
This marks an important point : If you’re using Servury and paying with crypto, there’s officially no way you could get your IP logged or browser fingerprinted.
I also re-made the whole public site to be way more hard hitting, would love to hear if you guys have feedback on it.
I just re-read a big part of the thread and I wanted to say Servury couldn’t have gotten this private/sovereign without the help of everyone who provided feedback in this thread, so I wanted to say a big thanks to you guys!
I’m excited about this VPS and am considering it for some future projects.
On curiosity, I’m wondering how your service compares with the related points in exploration in the below article - or rather what’s your idea and policy about what content (outside of clearly illegal or malicious) use cases would trigger a possible takedown of a site. The article’s approach is brash, but it always struck me as interesting to see how different VPSs replied.
To be fair, I can guarantee that the content described in that write-up would survive on our Blackbox plan.
Essentially, on our regular plans, abuse reports are automatically processed, but on the Blackbox plan, I personally review every abuse report manually, and as long as what is outlined in the abuse report isn’t illegal according to Canadian law, no suspension will occur.
A tiered plan of automated vs manual review makes a lot of sense, and lets consumers decide if the risk of their content (even perhaps DMCA annoyances) merits the plan. Good stuff.
Didn’t know it wasn’t allowed for developers to post about their own site/project in tool suggestions. I find it far fetched to call that self promotion, but I don’t make the rules.
Of what service? How can your regular VPS offerings possibly be >99.95? Why there are no documentation regarding live migration practices, patching? How can we verify your uptime claims?
Core i9 14900K
What are your multitenancy precautions? How can you possibly manage firmware states of desktop class CPU in desktop class motherboards? How can a desktop class motherboard achieve 99.99 uptime?
LUKS2 full disk encryption, zero-knowledge and fully user-managed: the entire setup runs inside your own VPS, you type the passphrase into your server’s boot shell over SSH, and it never touches our systems. SEV-SNP seals RAM off from our own hypervisor. Add BYOIP with automated RPKI and reverse DNS you control.
Please elaborate what is your cloud stack, where it’s documented.
Can this service be both an oversell of purely technical promises and a honeypot?
Active
incidents SG3 downMINORInvestigating
The server is currently unresponsive, we are investigating.
Started Aug 11, 2026 15:20 UTC · updated 14s ago
Yet SG3 kuma “uptime” is 99.99% uptime (90d) · up 8h ago Operational
@ybceo
Can you elaborate on how you obtain your residential proxy IPs?
I am interested in one alongside my general VPN use, for where there are VPN/datacenter IP blocks.
As far as I understand (and I understand not much about it), there are several methods to obtain such IPs, e.g. local proxy services on devices users agree to run in the background, renting or leasing IP ranges from ISPs, or other methods.
