The FAQ (linked from the very bottom of the page) is more interesting. The server part is just a file server. The client in this case handles all the file syncing, including locking. The client is the interesting part.

Cloud = servers someone else has and mostly maintains for you

Cloud...at home? This is a dumb headline. The definition of "server" has gone from big bulky slabs of bare metal to include smaller things like a RPi.

> Cloud = servers someone else has and mostly maintains for you

No, ”cloud = on-demand provisioned server resources”; that was what distinguished cloud computing from pre-existing remote-leased or on-premises resources. “Private cloud” (usually, on-premises of the user) has been a thing since very early in cloud computing, and “at home” has been plausible for even fairly casual users at least since Ubuntu 9.04 bundled Eucalyptus.

But this service is just abusing “cloud” to mean “SaaS”, I think (in that it's a demo of a paid SaaS product that incorporates your hardware.)

No, cloud does not mean that. Generally the cloud means that you can access data stored on a cloud as long as you are connected to the internet (or the same network). I don't know where you got that definition of cloud from.

I think the biggest issue in this thread is the multiple definitions of what a cloud is. To most of the people in this thread, the cloud isn't possible at home. To consumers, the cloud is just somewhere else to store their files. This addresses the latter, giving consumers an easy way to store their files on a "server" i.e. their computers, while having it in your home.

Reminds me the ridiculous "no software" campaign by Salesforce.

LMAO, now I need to hear about it.

Every computer can be a server and every server is a computer. The only difference is on a layman's mind. Just because you're interfacing with the computer through a screen instead of a network connection doesn't mean the backend service/OS calls changed a bit.