Integration Options
Choose an integration based on where your application runs and which services it needs.
| Requirement | Integration |
|---|---|
| Python packages, local files, or a Python backend | Native SpatialEngine and the Python SDK. |
| An application that runs entirely in a browser | The npm package and WebAssembly engine. |
| A desktop development environment with samples and preview | SpatialStudio. |
| Shared project history and streamed spatial data | SpatialDrive, connected through the engine. |
| Sandboxed user-authored workflows | WebAssembly extensions. |
| Engine functionality unavailable through statements | Source development. |
UI frameworks
The engine supplies a viewport and statement API. You can build controls with HTML, React, another web framework, or your desktop toolkit. Studio supports Python projects with web frontends, including frontends built by an external toolchain.
Target environments
A native engine can access files on its host. An in-page engine operates within the browser’s filesystem, network, and GPU restrictions. A path passed to a native file loader is a path on the engine’s machine.
Data import and storage operations can differ between builds. Check the installed API and test the target you plan to distribute.
Source development
Use source access to change engine behavior or build a custom engine. Follow the checkout’s Rust toolchain and build instructions.