I currently run 2 Synology NAS's in my setup. I am very satisfied with their performance, but nevertheless I will be phasing them out because their offerings are not evolving in line with customer satisfaction but with profit maximization through segmentation and vertical lock-in.

Storing encrypted blobs in S3 is my new strategy for bulk media storage. You'll never beat the QoS and resilience of the cloud storage product with something at home. I have completely lost patience with maintaining local hardware like this. If no one has a clue what is inside your blobs, they might as well not exist from their perspective. This feels like smuggling cargo on a federation starship, which is way cooler to me than filling up a bunch of local disks.

I don't need 100% of my bytes to be instantly available to me on my network. The most important stuff is already available. I can wait a day for arbitrary media to thaw out for use. Local caching and pre-loading of read-only blobs is an extremely obvious path for smoothing over remote storage.

Other advantages should be obvious. There are no limits to the scale of storage and unless you are a top 1% hoarder, the cost will almost certainly be more than amortized by the capex you would have otherwise spent on all that hardware.

Synology became so bad, they measure disk space in percent, and thresholds cannot be configured to lower than 5%. This may have been okay when volume sizes were in gigabytes, but now with multi-TB drives, 5% is a lot of space. The result of that is NAS in permanent alarm state because less than 5% space is free. And this makes it less likely for the user to notice when an actual alarm happens because they are desensitised to warnings. I submitted this to them at least four times, and they reply that this is fine, it’s already decided to be like that, so we will not change it. Another stupid thing is that notifications about low disk space are sent to you via email and push until it’s about 30 GB free. Then free space goes below 30 GB and reaches zero, yet notifications are not sent anymore. My multiple reports about this issue always responded along the lines of “it’s already done like that, so we will not change it”.

Most modern, especially software companies, choose not to fix relatively small but critical problems, yet they actively employ sometimes hundreds of customer support yes-people whose job seems to be defusing customer complaints. Nothing is ever fixed anymore.

I'm going to buck the nerds and say I wish Drobo was back. I love my 5N, but had to retire it as it began to develop Type B Sudden Drobo Death Syndrome* and switch out to QNAP.

It was simple, it just worked, and I didn't have to think about it.

* TB SDDS - a multi-type phenomenon of Drobo units suddenly failing. There were three 'types' of SDDS I and a colleague discovered - "Type A" power management IC failures, "Type B" unexplainable lockups and catatonia, and "Type C" failed batteries. Type B units' SOCs have power and clock go in and nothing going out.

I've no experience with Synology and have no opinion regarding their motivations, execution, or handling of customers.

However...

Long long ago I worked for a major NAS vendor. We had customers with huge NAS farms [1] and extremely valuable data. We were, I imagine, very exposed from a reputation or even legal standpoint. Drive testing and certification was A Very Big Deal. Our test suites frequently found fatal firmware bugs, and we had to very closely track the fw versions in customer installations. From a purely technical viewpoint there's no way we wanted customers to bring their own drives.

[1] Some monster servers had tripple-digit GBs of storage, or even a TB! (#getoffmylawn)