If you stop paying
Functions are stored, not lost: they answer 402 until the account is paying again. The database works for seven days, is then stopped, and is never deleted; you are pointed at transfer_database, which has no deadline.
Straight answers
What juudd won’t do, said before you build on it
Five refusals, each one on purpose, and what happens to your site when traffic spikes or the paying stops.
Five limits, stated before you build on it.
It will not install your dependencies
A build runs against a toolchain this platform pins, and a package.json naming anything outside it is refused with the whole list in the reply. What a build cannot produce becomes a function.
It will not show what a function printed
site_errors says which routes failed, when and how many times, not why. What a request returns is all you have to debug from, so write your functions to answer with what went wrong.
It will not delete anything
Every version you deploy stays, so a site can be replaced but never wiped clean. Taking one off the internet is a different thing and it is allowed: unpublish_site stops serving it, and keeps every version.
It will not serve an apex domain everywhere
On the paid tier your own domain works, but example.com with no www works only if your DNS provider flattens CNAMEs or offers ALIAS records. If yours does not, use www and redirect.
It will not take a domain that is behind another CDN
Ownership is proven through the domain's DNS, and another CDN in front of it hides exactly what has to be read. It has to come off that CDN first.
Heavy traffic, and if you stop paying
Neither plan counts requests
A bot flood is traffic you did not want and cannot prevent, so it is not traffic you pay for. That is part of the price, not a support policy.
Why we do not count requestsThat is the whole list.
Everything on the front page is what juudd does for you.