This message was deleted.

Hey @crooked-pager-76981, we’re still working up to the developer preview launch of e2ee. This is why you can’t find any pages on our docs site, blog or website. This will be coming soon. Is there some specific information regarding e2ee you’re looking for? cc @polite-kilobyte-67570 @freezing-lifeguard-43174

okay thank you, everything seems clear when I see the code, the worker part etc. is it full version and I can use it or should we wait for the documentation and maybe additional stuff that will be added

hi Arnas! e2ee support is currently still experimental. But there are already people who are using it successfully! We currently do not plan to add any more features for e2ee directly, there’s a couple of smaller changes in the pipeline to improve end user experience, but that’s about it.

@crooked-pager-76981 just to add, @bright-scooter-10854 can help you get set up/introduced to some folks on the professional services side with expertise in WebRTC and LiveKit.

Hey @polite-kilobyte-67570 and @crooked-pager-76981 on the livekit security section it mentions that e2ee is in active development, just want to understand what does that actually mean? my understanding of e2ee is the feature needs to be supported only on the client with Framecryptor interface, server doesn't have any role in achieving e2ee, correct me if I am wrong.

@kind-hospital-30284 disclosure: I don’t have as deep of an understanding as Lukas (or others on the LK core team). While the bulk of the implementation work for e2ee is on the client side, there’s likely some work required on the server side to ensure certain packet header information can be still be read and used for routing. Beyond this though, e2ee support needs to be integrated across client SDKs and thoroughly tested. This is something we’ve been actively working on over the last few months.