A Static Site Doesn't Mean a Static Backend

The static-export pitch is server-free pages, not a server-free product — the moment a site needs to accept input, whether that's a contact form, a newsletter signup, or a comment, something has to receive and process it, and that something isn't part of the static output.

Serverless functions are the usual answer: a small, separately-deployed endpoint that handles just the form submission, invoked on demand instead of running continuously. It's a real server, just one scoped to a single job instead of the whole app.

The trap is assuming the static/dynamic split is a property of the whole site rather than a property of each individual piece of functionality — most static sites end up with a handful of these small dynamic seams, and treating that as a failure of the static approach misses that it was never meant to cover everything.