obxiousJoin the waitlist

OBXIOUS COMPUTE / FOR SMALL 3D TEAMS

Where should 3D work run?

A designer needs a responsive viewport. A final render can wait. Compare local, edge and cloud placement for each task, then carry the scene settings into your next session.

Run the demo Open 3D studio

Try the placement simulator and a live CPU render without signing in.

STUDIO PREVIEWPROJECT 01
A ring-shaped desk lamp with a cast shadow, exported from the Obxious 3D studio

Lumen / Product study

Rendered in the browser

INTERACTIVE ROUTING DEMO

One scene, two routing policies.

Change the edge connection or studio load. See where each task goes and what that choice costs in the model.

Placement study
Illustrative model

TASK PLACEMENT

4 tasks
Scene taskMixedCloud only
Viewport inputOrbit, select, and move the camera
DeviceDevice
Interactive previewShade the frame as the artist works
EdgeCloud
Offline final renderExport the full-resolution product shot
CloudCloud
Asset syncSync geometry and material textures
CloudCloud

MODELED OUTCOME

Same workload & inputs

Mixed routing

Preview response
41ms
Resource cost
49.5pts

Cloud only

Preview response
74ms
Resource cost
42.3pts

The edge has the shorter preview path and meets the 50 ms target.

Model assumptions

Both policies handle input on the device and run the other tasks remotely. Final renders and asset sync use the cheaper cloud tier. Mixed routing chooses the cheapest preview path inside a 50 ms target, or the fastest available path if neither qualifies.

Preview response adds 4 ms for input, one network round trip, preview compute, queue time, and 6 ms for encoding and display. Cloud RTT stays at 52 ms. For this workload, compute takes 19 ms at the edge and 12 ms in the cloud.

Each session beyond 4 adds 6 ms of edge queue time. Cloud queue time grows by 2 ms per session beyond 8.

Cost points sum task weight × tier rate × sessions. The four task weights are 1, 8, 24, 3 in table order. Rates are 0.1 for device, 0.7 for edge, and 0.4 for cloud. These are relative resource units.

Timings and cost points use illustrative inputs.

Take the scene for a spin in your browser.

Open 3D workspace

LIVE COMPUTE PROOF

A frame from
the server.

Choose a view of the Mandelbrot set. The server computes the pixels, and your browser checks them before drawing the frame.

Fractal view
No sign-in required
Server CPU96 × 60 / RGBA
Seahorse
Request time
—
FNV-1a checksum
—
Output
Ready

Request time includes the network round trip, rendering, and receiving the pixels.

PROJECT MEMORY / ACCOUNT REQUIRED

Bring the brief into your next session.

Save the finish and lighting you chose for a product shot. Later, ask for the look in your own words, inspect the original brief, and apply its settings to the 3D scene.

Try project memory
LUMEN / DESIGN BRIEFEXAMPLE

QUESTION IN A NEW SESSION

“What look did we choose for the next product shot?”

FROM THE SAVED BRIEF

Use a copper finish and warm studio lighting. Turn off auto-rotation while composing the shot.

Saved source · Lumen product photography preferences

01 Keep the source

A content hash identifies the original brief and prevents duplicate entries.

02 Find it by meaning

AI summarizes the brief. Embeddings let a new question retrieve it using different words.

03 Restore the scene

Answers cite your saved sources. Apply the settings in the studio or export the memory as JSON.

INFRASTRUCTURE ROADMAP

From a placement plan to a remote render.

Our next milestone is one remote GPU worker for a product scene. The plan pairs CPU, GPU and RAM with SSDs for active assets and HDDs for archives. We’ll measure the delay from input to frame on that worker.

Longer term, the goal is to connect regional clusters and let authorized apps retrieve project memory. Orbital compute remains a research direction.

EARLY ACCESS

Try Obxious
with your team.

Working with product scenes, interactive previews or long renders? Join the list for early access and product updates.

Open the 3D studio

A first look, when it’s ready.

Your waitlist signup
How we’ll use your details

We store your email address, optional use case, and consent to contact you solely about Obxious early access and product news. Keep the private removal link shown after your first signup to delete your entry later. Submitting this form does not send an email.