They also have three pages worth of deployment adapters for one line deployment on many platforms, including many built by the community. https://astro.build/integrations/?search=&categories%5B%5D=a...
Did you even bother to look at their site or even better the guides I posted upthread or just decide to pull that out of your ass?
And yes I can see you're posting the same lie all over the comments here.
Stop being a potty mouth.
What Vercel really did was make Next.js work well in serverless environments, which involves a lot of custom infrastructure [0]. Cloudflare wanted that same behavior on CF Workers, but Vercel never open-sourced how they do it, and that is not really their responsibility.
Next.js is not locked to Vercel. The friction shows up when trying to run it in a serverless model without building the same kind of platform Vercel has.
Or they could add features that only work if you deploy via cloudflare.
I also take anything said in an acquisition announcement with a grain of salt. It is pretty common for companies to make changes they said they wouldn't a few years after an acquisition.