USE CASE // ROBOTICS · WORLD MODELS

Sim-ready assets for robotics and world models.

Compile scanned and generated meshes into simulation-ready assets with convex colliders. The pipeline is content-addressed, so the same input and options always return the same output. Run it hosted, or self-host it inside your VPC or an air-gapped cluster.

From $0.05 per asset, as low as $0.02 on Studio. Sandbox includes 500 free credits.

PIPELINE // SIM-READY REPRODUCIBLE
  1. IN shelf_unit.glb scanned or generated
  2. weld repair non-manifold edges
  3. decimate target_tris: 20,000
  4. convex_hulls max_hulls: 16
  5. voronoi_fracture seed: 0x5EED
  6. sha-256 same input → same output
  7. OUT sim-ready .glb + colliders + telemetry.json
Stages of compile_3d_asset + simulate_fx_vat (illustrative).

01 // PAIN → FIX

Why raw meshes stall a simulation pipeline

Synthetic data depends on clean assets and on your ability to regenerate the data exactly.

  1. PAIN

    Scanned and generated meshes arrive non-manifold, far too dense for contact and without collision geometry.

    FIX

    weld and decimate to a contact-friendly budget, then convex_hulls emits convex colliders for your simulator.

  2. PAIN

    Ad-hoc conversion scripts drift between runs, versions and machines, so a team cannot regenerate a dataset to debug it.

    FIX

    A SHA-256 hash of input and options keys every result, so the same input returns the same key and output. Fracture rollouts are seeded.

  3. PAIN

    World models need many physically varied scenes, and CPU-bound asset prep becomes the bottleneck of the data pipeline.

    FIX

    Batch over REST from your data pipeline, add seeded Voronoi fracture and XPBD cloth rollouts for variation, and dry_run a large job first.

  4. PAIN

    Robot logs, facility scans and proprietary CAD can’t leave your network.

    FIX

    Self-host the stripped Linux container (libspatial_kernel.so + Rust gateway) on your own NVIDIA L4/L40S/H100 hardware, with zero external network calls.

02 // OPERATIONS

Operations for simulation assets

Geometry cleanup, colliders and seeded physics rollouts all sit behind one content-addressed cache.

  • convex_hulls physics-ready

    Builds convex collision hulls from the cleaned mesh, the collision geometry a rigid-body simulator expects.

  • weld + decimate compile_3d_asset

    Produces manifold topology at an explicit target_tris, so contact and collision stay tractable.

  • voronoi_fracture simulate_fx_vat

    Runs seeded Voronoi rigid-body fracture rollouts on the GPU for breakage and debris variation in synthetic scenes.

  • xpbd_cloth simulate_fx_vat

    Runs GPU XPBD cloth rollouts for deformables such as drapes, covers and soft goods.

  • sha-256 cache reproducibility

    Keys results by a hash of input and options, so re-runs of unchanged inputs are cache hits at 0 credits.

  • self-host VPC · air-gapped

    Runs the same kernel and gateway as a stripped Linux container on your own GPUs (Enterprise plan).

03 // EXAMPLE ILLUSTRATIVE

Same input, same output

A data pipeline compiles a scanned asset over REST. Run it again with the same input and options and you get a cache hit with the same output hash.

terminal · REST · illustrative
curl -X POST https://api.spatialcompiler.dev/v1/compile \
  -H "Authorization: Bearer sk_test_spatial_sandbox" \
  -F "file=@shelf_unit.glb" \
  -F 'options={"target_tris":20000,"collider":"convex","max_hulls":16,"dry_run":false}'
telemetry.json · illustrative
[
  {
    "run": 1,
    "status": "ok",
    "input_sha256": "3f9a…c41e",
    "tris_in": 412000,
    "target_tris": 20000,
    "tris_out": 20000,
    "collider": "convex",
    "max_hulls": 16,
    "cache": "MISS",
    "credits_est": 5,
    "output_sha256": "b71d…09aa"
  },
  {
    "run": 2,
    "status": "ok",
    "input_sha256": "3f9a…c41e",
    "cache": "HIT",
    "credits_est": 0,
    "output_sha256": "b71d…09aa"
  }
]

Illustrative output. Not measured.

Numbers in the request are inputs and targets you choose.

04 // FAQ

Robotics & world-model questions

All questions →

README.SIM
Are outputs deterministic and reproducible?

Yes. A SHA-256 hash of the input and options keys every result, so the same input returns the same key and the same output. Fracture rollouts are seeded.

Can we run it inside our VPC or an air-gapped cluster?

Yes, on the Enterprise plan. You deploy the stripped Linux container (libspatial_kernel.so + Rust gateway) on your own NVIDIA L4/L40S/H100 hardware with zero external network calls.

Does it replace our simulator?

No. Spatial Compiler prepares the assets your simulator loads. It cleans geometry, builds convex colliders and runs seeded physics rollouts, then returns standard .glb files with JSON telemetry.

What does a sim-ready asset cost?

A standard compile, with its convex collider, is 5 credits: $0.05 pay-as-you-go, or about $0.02 on Studio. Fracture or VAT bakes are 10 to 20 credits at indicative rates, and SHA-256 cache hits cost 0 credits.

Make your next scene sim-ready.

From $0.05 per asset, as low as $0.02 on Studio. Signup includes 500 free sandbox credits (~100 compiles), and cache hits and dry runs cost 0 credits.

All use cases →