That's right but instead we built on top of audio-video streaming primitives so that it provides the same convenience of AWS lambda but can support persistent webRTC & websocket connections.
All you have to do is write your backend logic using our open source SDK and then you can one click deploy to Outspeed's infra similar to Vercel.
The hardest part has to be building webRTC streaming support from scratch into our SDK to provide extremely low latency API. We had this idea where we imagined the webRTC server and AI model running on the same instance and talking to the user via a direct peer connection. As far as we know, this architecture is first of its kind and isn't usually how webRTC peer connections are made.
Yes if the JWT token can only become invalid based on an expiration time. You can add the expiration time in the token and check it during authentication.
No if the token can become invalid due to other reasons because lets say the user deletes the token because it got leaked. But since you have no way of invalidating the token other than changing the encryption key, you can't selectively invalidate that one token.