How I used Rust, WASM, and WebGPU to build a low-latency trading terminal that runs entirely in the browser
https://i.redd.it/cxjbbleldkah1.gif
Hey everyone,
I wanted to share a project I’ve been building called CoreCandle. Like a lot of you, I was tired of two major friction points in my trading setup:
The clunkiness of running native desktop platforms (especially on non-Windows machines).
The frustrating execution latency caused by cloud webhooks and centralized mid-layers when using web tools.
If you browse these subreddits often, you might remember my previous posts about the legacy Windows desktop version of this platform. While the desktop app worked well, it had two massive bottlenecks: it locked out Mac/Linux users, and managing local multi-account execution without connection lag was a constant headache.
Instead of trying to patch an old architecture, I decided to completely pivot and rewrite the entire system from scratch for the browser. I used Rust, WebAssembly, and WebGPU to see if I could bring raw desktop performance into a standard web tab. CoreCandle is the result of that total overhaul.
solve this, I built a high-performance trading terminal that shifts all the heavy lifting directly to the user's hardware inside the browser.
To
### The Architecture:
* **WebGPU Core:** Renders thousands of data points, complex indicators, and raw order books smoothly at a locked 60+ FPS without choking the DOM or burning up the CPU.
* **WASM Pipeline:** Handles ultra-fast data serialization and client-side processing.
* **Direct Broker Connections:** Instead of routing your trades through a central server mid-layer (which introduces webhook and execution lag), the app establishes direct, secure client-side WebSocket connections straight to your crypto/forex brokers and MT5 endpoints.
### Why this matters for execution:
By keeping the entire pipeline client-side, your private API keys never touch a third-party server, and order execution times drop significantly because you're bypassing the typical "TradingView -> Webhook Server -> Lambda Function -> Broker" latency loop.
I’m currently gathering feedback from active traders, quants, and engineers to see what features or integrations would be most valuable next.
Happy to answer any questions about the WebGPU render loop or the client-side socket implementation!