To state the blindingly obvious: It's a perfectly valid term for what OP / the github repo refers to and your response just goes on to show that you probably don't know much about these things.

Let me spoil it to you: The cloud is also not an actual cloud, it's just someone else's server.

This seems like a very pedantic and harsh comment? I’d expect most people at HN to understand what “serverless” means, and it appears that tight integration with this architecture is the whole USP of this project, and as such I’d say the author made an excellent choice of putting it in the name: it makes it immediately clear what its key differentiator is.

“Serverless” has, for quite some time, meant something other than “without a server behind it.”

> a method of providing backend services on an as-used basis

As opposed to renting a dedicated server or VPS instance