Sand3D's core geometry backend architecture and the potential for supporting multiple, alternative backends beyond Blender.
Raw Developer Origin & Technical Request
GitHub Issue
Nov 10, 2026
## Context
Sand3D currently relies on Blender for geometry and scene operations. Supporting other backends could enable new workflows, but would also introduce design and maintenance costs. PR #26 started this discussion with an interface intended to run Sand3D in Albatross3D.
## Questions to explore
- Which concrete user needs would justify another backend? What would users gain over exporting the result from Blender?
- Which candidates are worth investigating? Examples include a standalone mesh engine, Open CASCADE for CAD workflows, or browser-based generation. What capabilities would each actually provide?
- Should every backend support all verbs, or could a useful subset be supported? How should unsupported operations be reported?
- How should we handle differences in geometry, booleans, face naming, precision, materials, scenes and exports?
- What compatibility, testing and maintenance commitments would an interface require?
This issue is for investigation and discussion. It does not commit the project to a particular backend, API or implementation.
Developer Debate & Comments
No active discussions extracted for this entry yet.
Adjacent Repository Pain Points
Other highly discussed features and pain points extracted from Sandflow-ai/sand3d.
Frequently Asked Questions
Market intelligence mapped to Sand3D's core geometry backend architecture and the potential for supporting multiple, alternative backends beyond Blender..
What is the technical positioning of Sand3D's core geometry backend architecture and the potential for supporting multiple, alternative backends beyond Blender.?
How is the developer community reacting to Sand3D's core geometry backend architecture and the potential for supporting multiple, alternative backends beyond Blender.?
What architecture is tied to Sand3D's core geometry backend architecture and the potential for supporting multiple, alternative backends beyond Blender.?
Engagement Signals
Cross-Market Term Frequency
Counts stored text matches for foundational terms like geometry and exports in analysed public discussions. These counts do not measure adoption.
Stored text matches, not adoption or market-share measurements.
- geometry: 14 records
- exports: 11 records
- precision: 8 records
- Blender: 6 records
- scenes: 6 records
- materials: 3 records
- verbs: 2 records
- geometry backends: 1 records
- standalone mesh engine: 1 records
- Open CASCADE: 1 records
- CAD workflows: 1 records
- browser-based generation: 1 records
- booleans: 1 records
- face naming: 1 records
- Albatross3D: 1 records
SaaS Metrics