Why we put the lab in a browser tab

Most scientific computing still begins the same way: provision a machine, install a toolchain, wait for a driver, upload your data somewhere it no longer belongs to you. The work that matters — composing an idea, training it, inspecting it — sits behind a wall of setup.

Scellis removes the wall. The browser is the compute substrate: WebGPU replaces CUDA, the database replaces the filesystem, and there is no Python runtime. You open a tab and you are already in the lab.

A small engine, unbounded capability#

The compiled app is just an engine — a microkernel. Every capability you actually use — blocks, models, viewers, datasets — is content delivered from a database at runtime. New capability never requires a new app build.

What we'll write about here#

• Release notes and roadmap signposts as the platform grows.
• Engineering deep-dives: the IR ladder, WebGPU training, oracle-checked numerics.
• How-to walkthroughs that complement the guide.

Open a tab and follow along.