Notebooks, Now Decoupled from Live Instances · Bifrost

Notebooks, Now Decoupled from Live Instances

Edit notebooks and dispatch render jobs without a GPU instance, pre-warm instances for when you need them, and share packaged datasets across your organization.

Editing a notebook and dispatching renders without a live instance

Until now, opening a notebook meant spinning up a live instance - even if all you wanted was to tweak a parameter or kick off a render. That's GPU time spent waiting on you, not working for you.

We've just released a new flow that separates live instances from notebook access.

What's New

Why this matters

Most notebook sessions don't need a GPU. Reviewing scenario parameters, adjusting a camera pose, dispatching a batch of renders - none of that requires a live viewport. Decoupling the two means you only consume instance time when you're actually iterating visually, and renders go out the moment you're ready instead of after an instance boots.

Pre-warming flips the equation the other way: if you know you'll need the viewport at 2pm, start the instance at 1:55 and walk into a session that's already hot.

Also new: packaged datasets shared across your organization

We've also improved the downloads flow. Packaged datasets are now shared across your entire organization, with the ability to filter by the dataset's creator.

You asked for a way to share downloads across the whole team - now anyone in your org can grab a teammate's packaged dataset without re-rendering or passing files around.

Spend GPU time on rendering, not waiting

Want to see the new flow in action?