All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
On Servury
averagedatahoarder
Member
I purchased a Blackbox VPS from Servury a but under a month ago. I love the concept and I haven't seen any other provider that offers this, so I was excited to try it out.
When I first spun it up it took a while before it was ready to setup, I was confused for quite a while when I couldn't login to the machine / it was stuck on some sort of awaiting encryption state -- turns out I needed to attempt to SSH in and then follow their encryption setup flow first. Set it up and everything worked fine.
Since then I've been using it as a relay node for privacy. It works most of the time, but there's been quite a bit of downtime with their scheduled maintenance (much more than other providers). I've had multiple hours of downtime, which is a bit annoying as I can't access any of my content on the box during these outages.
Also, take this with a grain of salt but I remember seeing at the beginning of the month that Blackbox had unmetered bandwidth... and I checked in the internet archive and it was marked as unmetered... but I was just notified I had met my bandwidth limit and turns out the limit is now 4TB. Though I may be misremembering this.
Ah also, their Blackbox system is pretty clearly vibecoded (along with the rest of the site). I have nothing against LLMs, I just hope a human reviewed it at least before they shipped 
So, tl;dr: great idea, mediocre execution, less than optimal uptime. A bit annoying to work with, but it serves its purpose.
Comments
https://lowendtalk.com/discussion/220847/blackbox-2-vcpu-4-gb-50-gb-nvme-encrypted-ram-disk-100-anonymous-9-99-mo says 10G unmeter
They don't allow uploading custom boot image though, and I don't really like how they implement the boot procedure. Onidel allows measured direct boot with custom image and also highly available.
This has since been overhauled, I simplified the machine statuses since you weren't the only one to find them confusing.
We're aware of the downtime - We launched Blackbox recently, and we had to fix a few issues / modify BIOS settings on the nodes 2 times so far. You can expect immaculate uptime from now on.
Answered this in another post of yours - some users used insane amounts of bandwidth in short amounts of time, so we had to implement these limits to mitigate that. I also implemented one of the community's suggestions in a topic I wrote a couple months back :
https://lowendtalk.com/discussion/215138/what-features-would-you-like-to-see-the-most-on-your-server-provider/p1
Basically, you get a set amount of TB of bandwidth @ 10 Gbps, and then unmetered @ 10 Mbps.
I do use LLMs to write code for Servury, but I also review the output before shipping to production. That said, I would appreciate if you could specify what feels vibecoded so I can update it.
Fair enough. If you have other things to say / suggestions, please share them. Servury is heavily feedback driven and unlike a lot of hosts, we will go out of our way to implement your ideas/feedback.
That was true until Sep 26, not since. A measured Blackbox now boots your own image: either a UKI, or a bzImage plus initramfs plus command line, given by URL and SHA-256. It is loaded with -kernel/-initrd/-append under the same public AmdSevX64 firmware as our release, with kernel-hashes=on, so the SNP launch measurement is a function of the public firmware, your bytes and your command line, and you recompute it with sev-snp-measure without anything of ours in the path. You can also write your own pre-encrypted disk image over the volume, so the template and the console never touch your data. Sections 7 and 8 here: https://servury.com/guides/measured-boot/#byoi
Boot procedure : the firmware, kernel and initramfs are hashed into the CPU-signed launch measurement, the release is rebuilt byte for byte from pinned public sources (repo linked on that page), and the initramfs binds its per-boot SSH host key to the attestation report's REPORT_DATA, so the key your client shows you is the one the report vouches for before you type a passphrase. If there is a specific step you think is wrong, let me know.
oh nice, afaik you are the second provider on LET implements measured boot properly. Looking forward to @advinservers joining the train!
Sorry, NO. One might be lenient and consider vibe-reviewing (btw 'reviewing' code isn't even a thing in hardcore security) but vibe-[whatever] and coding don't go together in that field, period.
Real secure software looks like this (in the form of questions):
Just using (or have some llm use) a "magic" language like Rust may help to avoid some typical/common errors but it does not make your software somehow secure.
I remember there's a way to
ddthe image directly onto a running machine. This is often done to wipe any possible traces of spyware on the VPS itself, esp from hosting companies from China.