Yes, EdgeDB has native GraphQL layer, but I'm not sure I need it. I still want to have a precise control over the the communication, memory usage and DB performance, plus as soon as you add new functionality on top of basic CRUD, it's not enough to talk directly from frontend to DB anymore.

I'm not sure if those are my biases, but I still try to keep things into separated layers (i.e. DB, backend, communication and frontend), so I can change them without affecting the overall design too much.