Spatius provides a real-time avatar interaction layer around a customer-owned AI application. Soul Machines presents Digital People and Digital Workforce capabilities with tools for configuring people, voices, styles, interactions, and skills. The right choice depends on whether your team needs a focused visual runtime or a broader digital-person operating model.
Soul Machines product names and packaging can evolve. Confirm the exact Digital Workforce or developer offering included in a proposal.
| Decision area | Spatius | Soul Machines |
|---|---|---|
| Primary role | Avatar interaction and rendering layer | Digital People platform and workforce-oriented experience tooling |
| AI ownership | Customer owns ASR, LLM, TTS, knowledge, tools, and orchestration | Official developer materials describe platform interactions and programmatic skills; validate external-AI boundaries |
| Character configuration | Evaluate current Spatius characters and customization workflow | Official APIs expose available Digital People, styles, and voices |
| Rendering model | Motion data drives AvatarKit on the client | Use the vendor's supported Digital Person delivery and deployment model |
| Integration focus | Embed a visual layer in an existing product | Configure and deploy a digital-person experience within a broader platform |
| Best fit | Composable products with established agent infrastructure | Enterprise digital-person programs needing platform-level configuration |
The difference is organizational as much as technical. A component architecture lets product engineering assemble specialists for speech, reasoning, tools, analytics, and avatar presentation. A platform architecture can consolidate more configuration, governance, and experience management into one vendor relationship. Component ownership provides flexibility but creates integration work. Platform consolidation can accelerate a defined program but increases the importance of roadmap alignment, export options, and contractual clarity.
Do not leave “the platform handles it” as an architecture box. Name every runtime and responsibility.
Your product owns conversation capture, transcription, reasoning, knowledge retrieval, tool execution, safety rules, speech synthesis, analytics, and escalation. Spatius consumes speech audio to produce motion data, while AvatarKit renders the character inside your client. The boundary is intentionally narrow.
Official Soul Machines materials describe Digital People available through a workforce environment, an Interactions API, and skills that can be registered and invoked. Model the platform as an experience system and verify how your data, business APIs, conversation engine, digital-person assets, analytics, and client surface connect.
Pay particular attention to identity and lifecycle. Who approves a character? Who owns its source material, derived model, voice, wardrobe, and permitted contexts? What happens when an employee or actor withdraws consent? Can interaction logs be exported into your observability stack? How does the experience degrade if a skill, model, or visual service becomes unavailable? These questions often matter more than an isolated visual-quality review.
Both approaches can produce a user-facing digital human, but they assign product work differently.
Spatius is not a full digital-workforce management suite, business system, or conversational agent. Soul Machines may be broader than necessary if the company already has those layers and only needs an embeddable avatar runtime. Avoid assuming that broader scope means less total work: platform configuration, skills integration, identity governance, and enterprise rollout still require owners.
Create one card for every responsibility. Mark the present owner, desired future owner, required evidence, and switching cost.
Last reviewed Aug 3, 2026. Validate product availability, platform scope, data terms, and deployment with each vendor.
