Spatial Capabilities Catalog
Every capability in the spatial module, organized by subsystem — all built on React Three Fiber + Yjs CRDTs + Aeion platform infrastructure.
Core Scene + Collaboration
| Capability | Description |
Rendering + Visual Editor
| Capability | Description |
Asset Pipeline + Persistence
| Capability | Description |
Character + Cognitive AI
| Capability | Description |
Physics + Animation + Audio
Physics stack: rigid bodies, cloth/rope constraints, fluid simulation, and biomechanical muscle simulation.
Procedural + Visual Scripting + AI Generation
| Capability | Description |
WebXR + Meeting Rooms + Spatial Desktop
| Capability | Description |
Plugin Runtime + Marketplace
User-authored plugins run in sandboxed Web Workers with capability-based API access. Plugins ship as signed bundles via the template marketplace.
Floor Plans + BIM + Environment
| Capability | Description |
Cinematic + Combat (Game-Engine Features)
| Capability | Description |
AI Bridge + Orchestration + Cross-Module
| Capability | Description |
FAQ
Spatial spans many domains (rendering, character, physics, AI, networking). Each capability is purpose-built and independently testable — so features can extend and swap providers without destabilizing the rest of the platform.
No. Capabilities activate on demand based on what a scene actually uses. Most scenes use only a fraction of the full catalog at any one time.
Aeion Spatial is closed-source SaaS. Enterprise customers on dedicated infrastructure get deep configurability and integration access without needing source-level visibility.
Custom modules subscribe to spatial events and read/write through the API. Blueprint workflows (low-code) cover many integration patterns without custom code.
Most capabilities are configurable via tenant settings + per-scene overrides. Deep customization is available via custom modules.
Yes — plugin signing + code review for marketplace. Per-plugin permissions explicit + user-approved. Auto-revoke kill switch for confirmed security issues.