I shall clarify a bit:
- The main component of an IPFS node is Kubo (formerly go-ipfs)
- there is a Web UI that connects to kubo's "admin" API
- the Desktop app packages both into an electron app to easily install locally
- kubo can also run on a server (like cloudron - which I'm working on)
- the Web UI can access it via freshly added Auth
- you can also install a local node AND one on cloudron - and peer them
- "pinning" data on the cloudron node to have it available from e.g. your laptop if your desktop is offline
- your local node acts as a local-first "cache", and if you have accessed the data you need once, you're fully local-first without needing the cloudron node
- (or if the cloudron node is offline, but the data is stored on any other server on the IPFS network)