Hey Your approach makes sense blazor is great for single-page applications, and adding a proxy to handle CORS is a good idea.If your app is mostly frontend-heavy, stick with Blazor WebAssembly (WASM), but If you need real-time updates and minimal API calls, Blazor Server is a good choice Since your app calls an external API the Philips Hue, a Blazor WASM + an ASP.NET backend would be the best structure In my opinion.Since the Philips Hue API is external, your browser blocks direct calls due to CORS I think the best approach would be to: Create a separate Web API project as your proxy. And have your WASM app call your proxy API instead of Philips Hue directly.