Deno Deploy, Netlify, Vercel
--platform deno, netlify and vercel write the entry of these platforms next to the compiled application. The files and how each is deployed are in Building.
deno:main.tsserves withDeno.serve; the address of the client is the address of the connection. Run by Deno in the starter's tests.netlify: an Edge Function for every path (--path); the address of the client iscontext.ip, the environmentNetlify.env.vercel: a function with the webfetchexport on the Node.js runtime; the address of the client isx-real-ip, which Vercel sets.
The entries of Netlify and Vercel are checked under the same runtimes (Deno, Node) with stand-ins for what those platforms give a function, not on the platforms themselves.
Deploying
Deno Deploy, Netlify and Vercel deploy from the repository themselves: give them the build command (dart run spring_boot_starter_edge:build --platform <platform>). There is no deploy workflow for them.
Container platforms
A container platform (Google Cloud Run, Azure Container Apps, Fly) needs none of this: the application runs there as the ordinary server it is.