BunnyCDN's edge functions are more-or-less standard Deno handlers [0], if that can count as "standard". But generally edge functions means the runtime is given by the provider and so we don't really have a standard for that.
You could try to implement your logic in a WASI-compatible web assembly script - then things like I/O etc are abstracted and "standardised" (and then you can write it in whatever language makes you happy, though Rust will be the happy path in terms of ecosystem).
If you're into self-hosting, you can try Coolify - they take care of the Docker stuff and support all kinds services https://coolify.io/docs/services/overview (including plain Docker/compose deployments). So with this you could probably find a way to own it completely.
You could try to implement your logic in a WASI-compatible web assembly script - then things like I/O etc are abstracted and "standardised" (and then you can write it in whatever language makes you happy, though Rust will be the happy path in terms of ecosystem).
If you're into self-hosting, you can try Coolify - they take care of the Docker stuff and support all kinds services https://coolify.io/docs/services/overview (including plain Docker/compose deployments). So with this you could probably find a way to own it completely.
[0] https://bunny.net/edge-scripting/