The domain ownership thing
Unfortunately that probably won't ever happen.
.convex.cloud is owned "by us", and .convex.site is owned "by you." It gets pretty complicated to have blended RPC / hosting domains.1 Reply
Specifically, this means that on
convex.cloud, every endpoint is a "Convex-reserved" endpoint, and every header is a "Convex-reserved" header. The convex team reserves the right to change RPC paths and take control of headers etc as necessary to implement the best possible Convex wire protocol. So it's not very safe or ergonomic for developers to try to share control over this namespace with us, in terms of HTTP paths, or headers, or whatever.
On the other hand, we try as much as possible to have .site be a 100% blank slate, where you own all control of the headers, where 100% of the path/method space can be designed by you and confidently maintained by you. Even when we run into some possible conflicts, like the Authorization header, we try to find ways to open things up so you can get whatever semantics you need or override our usage of it when appropriate.