I’m glad you reached out! To help you reduce egress costs in LiveKit, here are some friendly tips you might find useful: • Use Efficient Egress Types: Try using Track Egress since it skips transcoding, which helps lower compute costs. Unless you really need layout compositing, it’s best to avoid Room Composite or Web Egress. • Optimize Encoding Settings: Consider lowering the video resolution, bitrate, and frame rate. This can make files smaller and lighten the processing load. • Use Cost-Effective Storage: You might want to store recordings locally or choose cloud storage options that have lifecycle policies to move files to more affordable tiers over time. • Limit Egress Duration: Setting session limits is a great way to prevent unexpectedly long recordings that could increase costs. • Scale Egress Workers Efficiently: Using autoscaling can really help optimize how resources are used, which is a smart move. • Reduce Transcoding Load: By sticking to Track Egress for individual tracks, you can bypass transcoding and save on that load. Following these steps should make a noticeable difference in keeping your compute and bandwidth expenses in check. If you have any questions or need more guidance, I’m here to help! Sources: protobufs/livekit_egress.proto | egress-sample.yaml | Understanding LiveKit Cloud Pricing | pkg/config/service.go | Universal Egress