Client Integration

Your application controls SpatialEngine. The engine connects to SpatialDrive for remote project storage and streamed spatial data.

The engine’s statement endpoint and the server’s HTTP address serve different purposes. Python connects to the engine’s gRPC port. The engine is configured with the SpatialDrive server URL.

Server connection

Use std.server.set_url in Python or std.server.setUrl in TypeScript:

client.std.server.set_url(url="https://spatialdrive.example.com")

Then authenticate with the strategy supported by your application and identity provider. The generated std.server types document the available authentication strategies. Do not reuse Studio’s sign-in as proof of access to a separate server.

Remote projects

Use std.project.remote to create or open remote projects. The SDK provides the request types and return values for your engine release.

Project permissions and organization membership determine which remote projects the user can access. Server-side authorization remains authoritative.

Organizations, access control, and common errors explain that model.

Application configuration

A browser app can load a prepackaged npm engine and configure its server connection at runtime. A native application can do the same through the Python SDK.

The existing infrastructure reference also includes source-built viewer deployment examples. Use the npm integration guide for new applications built around the packaged engine.