Author your Spatial Apps
Uses your existing AI development tools, models, and permissions.
Write spatial workflows, run them against SpatialEngine, inspect the result in a live viewport, and shape them into interactive apps from one desktop workspace.
- 14
- included sample apps
- Python
- isolated per project
- App QA
- inside the live preview
Move from an idea to a running spatial app
The editor, engine, preview, logs, and assistant share the same project and the same run. You can see each change where it matters.
Describe the app
Start from a prompt, a blank project, or one of 14 included samples. AI development tools begin with the project and SpatialStudio guidance in context.
Run against SpatialEngine
Edit Python and frontend files, then run the saved app with its own environment and the SDK matched to the bundled engine.
Check the working result
Use the live preview, script output, and engine logs together. App QA can exercise controls, inspect the page, and capture visual evidence.
Everything needed to shape the application
SpatialStudio keeps the project files, live preview, and runtime output together while leaving the application itself as normal, readable code.
Drive SpatialEngine from Python
Work with point clouds, meshes, polylines, tiled terrain, and imagery. Control styling, filtering, clipping, picking, and camera state through the Python client.
Build the interface your users need
Pair the Python runtime with HTML, CSS, and JavaScript. Use the included bridge directly, serve a Flask app, or build a React frontend.
Keep each project self-contained
The project folder records its entry point and dependencies. SpatialStudio creates an isolated environment and installs the SDK that matches the engine it will run.
The assistant can work in the app it is changing
AI development tools use your existing models, tools, permissions, and skills. SpatialStudio adds the active project, engine run, and preview to that workflow.
From request to checked app
Understands the project
AI development tools work with the current files, SpatialStudio guidance, and the running app as context.
Keeps changes visible
Review file updates, command output, approvals, and follow-up requests in the same workspace.
Can check the result
App QA can run the saved project, exercise the relevant workflow, and inspect the live preview.
Real projects, running in the app
Each image is a direct capture from SpatialStudio. Open the Python, inspect the live result, then save a copy and adapt the project.
Robot Cell Safety Planner
Interactive previewA bright interactive workcell preview with imported equipment, safety zones, camera presets, and a custom control rail.
3D equipment models from Microsoft experimental PCF control assets, licensed CC BY 4.0.
Largest US Data Centers
Interactive 3DA working SpatialStudio project for exploring data-center campuses in an interactive spatial map.
SpatialStudio project capture.
Use normal files from the first prompt to handoff
Every app is a folder you can inspect, copy, version, open in your editor, and build for someone else to run.
Your code stays visible
Python, HTML, CSS, JavaScript, assets, and project.toml remain ordinary files. The samples use the same project shape as the apps you create.
Publish prepares the handoff
SpatialStudio builds the frontend and marks the project ready to hand to someone. Deployment stays under your team's control.
Build your first app in SpatialStudio
Bring a representative dataset and the workflow you want to improve. We will help you turn it into a focused running application.