Baryon Web app
Web app

Open a tab. Render your sound.

The web app runs the Baryon runtime in the browser — same engine as desktop, no install, no setup. Connect a mic, line input, or browser audio source and watch live audio resolve into geometry.

Open the web app Move to desktop
Path /web-app
  1. The physics-based sound-to-space runtime, running in any WebGPU-capable browser.
  2. Same engine as the desktop app — not a stripped demo.
  3. No install, no setup; the engine is one tab away.

The fastest way to use the engine

The web app is the public entry point to the Baryon runtime. It is the engine running in a browser tab — the same shared analysis, physics, and WebGPU render path the desktop app uses. Open it, connect audio, and the runtime starts rendering.

What you can do in the browser

  • Render mic input, line input, or a browser audio source as live cymatic geometry
  • Hear how a track sits inside the engine without committing to an install
  • Tune the look and behavior of the runtime in real time
  • Use the engine as a discovery and study surface before moving to the performance app

What the browser does not do

Output routing is the boundary. The browser sandbox cannot speak Syphon or Spout, cannot expose a stage-output surface, and cannot run a long-form session under performance constraints. Those workflows belong on the desktop path. Everything else — the engine, the render path, the visual class — runs the same in both places.

When to move to desktop

Move to the desktop app when stage output, multi-surface operation, session persistence, verified host-routing paths, or live performance control matter. The browser is the easiest way to understand the runtime; the desktop is the path for real performance workflows.